-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem local testing Vagrant/Rails Server #425
Comments
|
Yes! I'll copy and paste on here as I can't attach the yml files.
|
I guess you mean this line - could this be a problem with the fact that my translation branch doesn't have all the requirements to have it up and running?
EDIT: ignore the rest, I forgot I did
|
I deleted |
thanks for your help @stardust66! I'm chuffed it is one step closer towards being able to test locally. |
Oh, I don't think your postgres server is running. That's what the |
@Intimaria. I fixed your file. I probably should do a PR or something but just copy paste this. Basically, on the lines with
In addition, run the command
and you should be good to go! |
💯 🥇 🙌 |
Hmmm... Am still getting
even after running |
Oh, have you run |
Yeah! you mentioned it in your step by step in #413, I tried running it again, but it says
This is what it specifies the problem is, which I'm not sure I understand (my rails is outdated?)
|
Can you run |
I am getting |
Okay. Feel better. |
Thanks I'll be back later and will try again! Thanks for all your help! |
I found the issue and submitted a PR. The migrations need to have versions because of rails 5. |
Brilliant! |
Whoops, I missed this thread entirely, somehow. Haven't been checking my e-mail today! I can say, regarding this: . . .
Your suspicions are definitely correct. If your working folder has the translations for a page, but not the page itself, an error may come up that prevents the Rails server from starting. (So if you have There have been a lot of similar errors (none of which are your fault) showing up in your branch, due to us separating a lot of stuff out which your branch would depend on into other PRs. Sorry about that! (These things can be fixed, but it and be easiest to do so once the other PRs are merged into develop.) |
@Intimaria For now just change all instances of
again and the server will actually run this time. |
OK, I'll give it a try when I get home and do have a look at the PR too! |
Finally able to try this - addind the [4.2] on the end of |
Yay! Glad it worked. |
Hi, I have tried to set up a local testing environment now both with vagrant on a friend's machine and with the rails server (as per @stardust66's instructions in #413 ) and I have gotten the same error messages. I have a feeling it has to do with the way my local git repo is doing but I would really love someone to give me a hand with it as I want to get it going. These are the error messages which are on my machine which are very similar to the ones on my friend's machine running vagrant and VB (which I don't have access to right now)
I was surprised to get the same error messages on both machines
Some are related to
invalid locale data
, which I suspect has to do with recent changes regarding translation which may not be correctly up to date on my local system,However, not sure whether that, or the deprecation warnings or,
invalid API key
are the real problem. Or something else? Thank you!Here is the full error message on terminal after trying to run rails server:
The text was updated successfully, but these errors were encountered: