Add SETUP instructions #19
No reviewers
Labels
No Label
area/i18n
area/infrastructure
area/moderation & safety
area/ux
priority/1.high
priority/2.medium
priority/3.low
tag/upstream issue
tag/duplicate
tag/help wanted
tag/invalid
tag/won't fix
type/bug
type/enhancement
type/question
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: treehouse/mastodon#19
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "setup-instructions"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Adding in draft setup instructions for dev environments. Would love some help testing this.
WIP: Add SETUP instructionsto Add SETUP instructions8d21dc3468
to8f59e1a853
8f59e1a853
to8a701c5ac3
@ -0,0 +1,4 @@
LOCAL_DOMAIN=localhost
DB_HOST=/var/run/postgresql
See below, but can we keep this contained inside the project root?
We can set
unix_socket_directories = '.' # comma-separated list of directories
inpostgres.conf
...Yeah that works. Accursed, but it works. It places the socket and lock file in the same dir as the data (so
data/postgres15
in our case)@ -13,2 +13,4 @@
/db/*.sqlite3-journal
# Ignore the dev postgres db we created.
/data/postgres15/*
Wow, I wish gitea had suggestions.
/data/postgres*/*
(?)@ -0,0 +45,4 @@
avoid interfering with system config.
9. Run `bundle install`.
10. Run `yarn install`.
11. Run `export $(grep -v '^#' .env.dev | xargs)` to source in our dev vars. You may want to alias this.
Am 50.01% sure that Rails will automatically source
.env.$RAILS_ENV
. searches.Ah. https://github.com/bkeepers/dotenv.
.env.development.local
should get documented/put into gitignore, then.Tested, and yeah, it does.
@ -0,0 +75,4 @@
2. git restore package.json yarn.lock
3. yarn install
Then re-run `foreman`. No. We have no idea why this worked.
I wonder if a simple
rm -rf node_modules
will do the trick.Maybe? We've been unable to replicate that bug, so maybe it was our own doing. Either way, added it as a suggestion.