bullet_train 1.2.16 → 1.2.18
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/app/views/layouts/docs.html.erb +1 -1
- data/docs/heroku.md +3 -11
- data/lib/bullet_train/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 7fcdabd8180d63e20fe0785536f14a8a44bffd267d4ba2823d61df957fc4b172
|
|
4
|
+
data.tar.gz: 1c31c359b2b9a34e36b375d78d2f0c01861605d237f0a8bb0733fbee0f100027
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: bf7e98581bfd138b8bdce05cc85c6e5f4fd663a36e0bed7821687a904aa705e2901a540329c13b6413730df1220ce4bea2a6d1903c766f24f97d4e254fd8f02a
|
|
7
|
+
data.tar.gz: eb670e1a68ba62e0f1c07da21b2ad059730f66b4df8ac6192159920a4ebccea87f56d093f8a21ff8d5c0a84bfb60c97ee59e6a30f8093027519fef136cb56e3b
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
</head>
|
|
35
35
|
<body class="bg-light-gradient text-slate-700 text-sm font-normal dark:bg-800-gradient dark:text-slate-300">
|
|
36
36
|
<div class="md:p-5">
|
|
37
|
-
<div class="h-screen md:h-auto overflow-hidden md:rounded-lg flex shadow"
|
|
37
|
+
<div class="min-h-screen md:h-auto overflow-hidden md:rounded-lg flex shadow"
|
|
38
38
|
data-controller="mobile-menu"
|
|
39
39
|
data-mobile-menu-hidden-class="hidden"
|
|
40
40
|
>
|
data/docs/heroku.md
CHANGED
|
@@ -36,29 +36,21 @@ After this, you'll be able to deploy updates to your app like so:
|
|
|
36
36
|
git push heroku main
|
|
37
37
|
````
|
|
38
38
|
|
|
39
|
-
### 2.
|
|
40
|
-
We've decided not to configure the application to automatically run database migrations after a deploy for the time being. For that reason, you'll need to run the migrations and seeds manually, like so:
|
|
41
|
-
|
|
42
|
-
```
|
|
43
|
-
heroku run rake db:migrate
|
|
44
|
-
heroku run rake db:seed
|
|
45
|
-
```
|
|
46
|
-
|
|
47
|
-
### 3. Enabling Runtime Dyno Metadata
|
|
39
|
+
### 2. Enabling Runtime Dyno Metadata
|
|
48
40
|
We include [Honeybadger](http://honeybadger.io) and Sentry (both at a free tier) for redundant error tracking by default. Sentry requires the following Heroku labs feature to be enabled:
|
|
49
41
|
|
|
50
42
|
```
|
|
51
43
|
heroku labs:enable runtime-dyno-metadata
|
|
52
44
|
```
|
|
53
45
|
|
|
54
|
-
###
|
|
46
|
+
### 3. Improve Boot Time
|
|
55
47
|
You can cut your application boot time in half by enabling the following Heroku Labs feature. See [this blog post](https://dev.to/dbackeus/cut-your-rails-boot-times-on-heroku-in-half-with-a-single-command-514d) for more details.
|
|
56
48
|
|
|
57
49
|
```
|
|
58
50
|
heroku labs:enable build-in-app-dir
|
|
59
51
|
```
|
|
60
52
|
|
|
61
|
-
###
|
|
53
|
+
### 4. Adding Your Actual Domain
|
|
62
54
|
|
|
63
55
|
The most common use case for Bullet Train applications is to be hosted at some appropriate subdomain (e.g. `app.YOURDOMAIN.COM`) while a marketing site is hosted with a completely different service at the apex domain (e.g. just `YOURDOMAIN.COM`) or `www.YOURDOMAIN.COM`. To accomplish this, do the following in your shell:
|
|
64
56
|
|
data/lib/bullet_train/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: bullet_train
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.2.
|
|
4
|
+
version: 1.2.18
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Andrew Culver
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2023-03-
|
|
11
|
+
date: 2023-03-09 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: standard
|