-
-
Notifications
You must be signed in to change notification settings - Fork 578
New Command generates invalid app settings #540
Comments
Also database.yml uses the complete name of the app instead of the last part: development:
dialect: postgres
database: github.com/apaganobeleno/other_development
user: postgres
password: postgres
host: 127.0.0.1
pool: 5
test:
url: {{envOr "TEST_DATABASE_URL" "postgres://postgres:[email protected]:5432/github.com/apaganobeleno/other_test?sslmode=disable"}}
production:
url: {{envOr "DATABASE_URL" "postgres://postgres:[email protected]:5432/github.com/apaganobeleno/other_production?sslmode=disable This ends up causing connection string to postgresql is invalid. |
And the issue lucas was having was because the session names was being set to be:
And that seems not to work. |
Sounds like we have 4 ways to fix this:
@apaganobeleno thoughts? |
@markbates first one sounds cleaner and simpler to me, second could be confusing because we're generating app in a different path than provided by the user, third and fourth have the problem that even tho buffalo have generated the app at the specified path, the user is not even close to that path and will need to do a cd github.com/... before starting to use it which again is confusing. So my vote is for #1 and warn them we do not accept special characters on the app name. |
works for me! you want to take this one, or should I? |
i'll work on it tonight, i think this one should be in our next release, agree ? |
yeah. it shouldn't take too long. there's already some logic around what is a "valid" name when creating a new app. just needs to be extended a bit. |
If you generate an app from $GOPATH/src with its complete source name the app won't start:
App starts but when you go to localhost:3000 it crashes with:
The text was updated successfully, but these errors were encountered: