Joshie
Joshie
PostsComments
RRailway
Created by Joshie on 6/26/2024 in #✋｜help
[BUG] Watchpath is ignored for v2 builder + mono repo
No description
29 replies
RRailway
Created by Joshie on 6/25/2024 in #✋｜help
How to get to django interactive shell?
Is there a way to connect to a django mange? IE running the interactive shell? How do people normally handle creating a superuser? I did it through a db migration (dump and restore). But is there some more native way? I am now in need of running some interactive shell code on the prod server. Or I would prefer to do it that way, as opposed to writing raw SQL. project id: 1b326884-0c17-43ed-9b52-f443662e8f50
7 replies
RRailway
Created by Joshie on 6/25/2024 in #✋｜help
How to get to django interactive shell?
Is there a way to connect to a django mange? IE running the interactive shell? How do people normally handle creating a superuser? I did it through a db migration (dump and restore). But is there some more natvie way? I am now in need of running some interactive shell code on the prod server. Or I would prefer to do it that way, as opposed to writing raw SQL.
4 replies
RRailway
Created by Joshie on 6/25/2024 in #✋｜help
Going from data tab (db) to different service, serves a blank screen
No description
5 replies
RRailway
Created by Joshie on 6/24/2024 in #✋｜help
crun: unknown version specified: OCI runtime error
project id: 1b326884-0c17-43ed-9b52-f443662e8f50 The error seems to be a platform issue and not a service issue. 
=========================
Container failed to start
=========================
 
crun: unknown version specified: OCI runtime error
=========================
Container failed to start
=========================
 
crun: unknown version specified: OCI runtime error
Nothing has actually changed on my end, for this service, since the last deploy. So it shouldn't fail. Don't know what the issue might be, nor how to resolve. (going to bed, so not going to respond for a bit [probably]).
7 replies
RRailway
Created by Joshie on 6/22/2024 in #✋｜help
Bug - clicking on help.railway threads link, double opens a link
I tried this on a few threads and they all do the same thing (example thread for you to try it out https://help.railway.app/questions/incident-response-june-11th-2024-733fbd5d) If you click on the link (in this case, the blog post link) it will open 2 new tabs. I tried this in: * Firefox - opens both * Chrome - opens one and tries to open the second, but is blocked
3 replies
RRailway
Created by Joshie on 6/21/2024 in #✋｜help
CRON Scheduling
No description
35 replies
RRailway
Created by Joshie on 6/20/2024 in #✋｜help
Posthog provider doesn't seem to work with railway
I have a frontend that uses posthog for its analytics. I used to have this whole project hosted elsewhere and everything worked perfectly. However, it does not seem to work on railway. I am defining my provider with 
const options = {
  api_host: "/ingest",
  ui_host: import.meta.env.VITE_REACT_APP_PUBLIC_POSTHOG_HOST,
}
...
<PostHogProvider
            apiKey={import.meta.env.VITE_REACT_APP_PUBLIC_POSTHOG_KEY}
            options={options}
          >
            <RouterWithPosthog />
</PostHogProvider>
const options = {
  api_host: "/ingest",
  ui_host: import.meta.env.VITE_REACT_APP_PUBLIC_POSTHOG_HOST,
}
...
<PostHogProvider
            apiKey={import.meta.env.VITE_REACT_APP_PUBLIC_POSTHOG_KEY}
            options={options}
          >
            <RouterWithPosthog />
</PostHogProvider>
(this is React + Vite, setup very similar to the template; but not exaclty the same) What this should do, is send all analytic requests to posthog. But I don't see any requests being made in the network. Normally, I would then have 
handle_path /ingest* {
        rewrite * {path}
        reverse_proxy https://us.i.posthog.com:443 {
          header_up Host us.i.posthog.com
          header_down -Access-Control-Allow-Origin
        }
}
handle_path /ingest* {
        rewrite * {path}
        reverse_proxy https://us.i.posthog.com:443 {
          header_up Host us.i.posthog.com
          header_down -Access-Control-Allow-Origin
        }
}
In a Caddyfile to actually handle that redirect. And this used to work. But it doesn't on railway. For some reason. I have tried to also not do this redirect thing btw, and just send request directly to posthog. However, it doesn't change anything. I have tried on both the new proxy and not. I have tried adding the handle_path to multiple locations (reverse proxy and frontend file server). I am not sure how to solve. Hopefully someone knows something that might help. And if not a direct tribal knowledge, at least tips on how to debug this would help 😄 project id: 1b326884-0c17-43ed-9b52-f443662e8f50
17 replies
RRailway
Created by Joshie on 6/20/2024 in #✋｜help
Info deploy logs are showing up as error
No description
11 replies
RRailway
Created by Joshie on 6/18/2024 in #✋｜help
US East, super slow
I just moved "everything" over to US East. And .... it was slow. Like broken levels of slow. The requests were all delayed by seconds. And <Link>s would simply not work (or take close to 10 seconds to load). For now, I moved everything back to US West. And it is fast again. I put everything in "" because there was one thing not in US East. the DB was in West. This could be something that slows it down. But no, this was seconds of delay between requests. Requests that do not take long at all to make. I really wish I could sit here and help debug but I can't afford to have prod be in a broken state for my testing purposes. I might test again and put everything in US East on off working hours (IE when my servers won't be used). And while I do that, I will test with the DB in US West and then move it over. But beyond that, idk how much testing I will be able to do to help debug this issue. I don't know what the issue actually is though. Becuase it isn't like like request are taking a long time to respond based on the request durations (both client and server were claiming quick responses. Lies!!!!) project id: 1b326884-0c17-43ed-9b52-f443662e8f50
45 replies
RRailway
Created by Joshie on 6/17/2024 in #✋｜help
Hanging invite in members section
No description
25 replies
RRailway
Created by Joshie on 6/14/2024 in #✋｜help
Builder using dockerfile over nix despite config path
There are a few things of context required. First, see #v2 Builder bug: uses nixpacks over dockerfile. When using the new builder in a subdirectory, the system uses nix over docker. I have different build for local and railway. Local uses a dockerfile and railway (for this subdirectory at least) uses nixpacks. As such, I have the config as code set to: /frontend/nixpacks.toml. Despite that, it still wants to use the docker image. (but doesn't becuase of the linked to thread). Anyways, I have a Vite frontend that is built and then served by caddy. If I use the new builder and let it be built through nix, it works properly. But if I use the old one, it uses dockerfile. There are some things going on here that might be a me issue. But I am not sure why despite giving it a config path, it still goes for the dockerfile. And even more so, why is it ignoring the config path for the nixpack? Is there a way to resolve this? As in, to more explicitly tell railway what to use for deployment? If not, I will just have to restructure my dockerfile to be usable with both local and prod. No big deal (probably). If this is not a "bug" than I guess it becomes a feature request. A way to be more explicit on the builder stuff. Or is that already a thing and would just require me to add a railway.json file?
8 replies
RRailway
Created by Joshie on 6/14/2024 in #✋｜help
Bug New project from template errors before creation
No description
38 replies
RRailway
Created by Joshie on 6/14/2024 in #✋｜help
Reverse proxy backend is unresponsive
No description
48 replies
RRailway
Created by Joshie on 6/14/2024 in #✋｜help
Excessive vCPU and memory on Django boot
No description
50 replies
RRailway
Created by Joshie on 6/14/2024 in #✋｜help
v2 Builder bug: uses nixpacks over dockerfile
I have a Dockerfile in my directories root. But yet, the build logs keeps showing the use of nixpacks: 
╔══════════════════════════════ Nixpacks v1.24.1 ══════════════════════════════╗
║ setup      │ python311, postgresql, gcc                                      ║
║──────────────────────────────────────────────────────────────────────────────║
║ install    │ python -m venv --copies /opt/venv && . /opt/venv/bin/activate   ║
║            │ && pip install -r requirements.txt                              ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │ python manage.py migrate && gunicorn BBWare.wsgi                ║
╚══════════════════════════════════════════════════════════════════════════════╝
╔══════════════════════════════ Nixpacks v1.24.1 ══════════════════════════════╗
║ setup      │ python311, postgresql, gcc                                      ║
║──────────────────────────────────────────────────────────────────────────────║
║ install    │ python -m venv --copies /opt/venv && . /opt/venv/bin/activate   ║
║            │ && pip install -r requirements.txt                              ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │ python manage.py migrate && gunicorn BBWare.wsgi                ║
╚══════════════════════════════════════════════════════════════════════════════╝
When I have a look at the details of the deployment, it shows that the builder is dockerfile (correct). But why is nixpacks being used? It is ignoring my dockerfile!? Why might this be going on?
83 replies