Deployments aren't doing nothing

[proper bone]

I am trying to deploy hedgedoc, and the deploy doesn't do nothing and it fails after a few minutes. Not positive what to do about this

[ocean adder]

Project ID: 3c13fb70-b70a-46cd-8d38-5e57856447ad

[proper bone]

3c13fb70-b70a-46cd-8d38-5e57856447ad

oh ok this is something

I don't know why it would be saying this, because railway is clearly able to figure out it does in fact exist

[ancient mango]

you better post this in #🤡｜memes-only before i do

[proper bone]

hmm, it's still not toing anything for me

Ohhh

lets go

ok

[proper bone]

😭

is there any way to make railway not obscure what is actually happening

this error is annoying

[ancient mango]

your application didn't respond lol

what else could it tell you?

https://docs.railway.app/guides/fixing-common-errors

[proper bone]

I just wish it would show me it not responding

the error returned by the server

or if the server is hanging, just show that

instead of inserting it's own response

[ancient mango]

there was no error, your app did not respond what so ever

[proper bone]

then show that

[ancient mango]

it is

[proper bone]

not really, because if I go to an IP I own on a real server and type in some random port, it just hangs forever

the server simply does not respond

[ancient mango]

why would that be an acceptable alternative?

[proper bone]

because that is what servers normally do

I've had issues with railway before where it seems like this page is cached

and it takes it a good 30 seconds to update the cache

[ancient mango]

right but how does hanging help you more than that page?

[ancient mango]

its not

[ancient mango]

and it takes my app a good 30 seconds to respond*

[proper bone]

maybe its because I'm used to servers doing normal things, but it is a lot more clear to me when I see this

even though it's like... objectively less clear

[ancient mango]

how is chrome's error page better?

[proper bone]

because that is the default behavior when you request a server and there is no port. The server just doesn't respond because it doesn't have anything to respond with, and the browser gives up

[ancient mango]

and the default behavior on railway is to tell you that your app didnt respond

[proper bone]

the departure from standard is just confusing to me. I don't know. I think we just want different things

[ancient mango]

im sure heroku and fly has similar pages

[proper bone]

I guess one other thing I have actually legitimate complaint with railway is my umami instance was taking ridiculous amount of resources. Eventually I gave up on railway and switched to hetzner. It wasn't really railway's fault, but I quickly figured out what the issue was on hetzner because I could ssh in and when I saw htop, I saw postgres was running 15 count(*) queries per second

and as far as I'm aware you can't just ssh into railway like that?

[ancient mango]

correct

[proper bone]

yeah

oh here was the bruh moment in question

[ancient mango]

though i dont think youd need ssh to find out how many queries are being ran

[proper bone]

unrelated but will this work in the template composer?

provided the PGUSER variables are set and such

[ancient mango]

yeah, why wouldnt it?

[proper bone]

just checking, I haven't used the new composer

[proper bone]

ohhh @ancient mango the cache I was thinking of was the Nothing here... yet

[ancient mango]

also not cache, just need a bit of time for railway to update the routing tables

[ancient mango]

seems a little broken

[ancient mango]

• change PORT to ${{CMD_PORT}}
• add CMD_PROTOCOL_USESSL set to true
• add CMD_SESSION_SECRET set to ${{secret(64)}}
• add a health check set to /_health
• rename template and service Hedgedoc -> HedgeDoc (since thats how they case the name)
• set a service icon for HedgeDoc

[proper bone]

did you fix this? doesn't happen for me

[ancient mango]

your browser might be auto upgrading http requests, please make sure to apply all my suggested changes

[proper bone]

alr

I've made all the suggested changes

doing a test deply

[ancient mango]

that was fast

[proper bone]

¯_(ツ)_/¯

[ancient mango]

do you like the new template composer?

[proper bone]

Yeah, much better than the old one

the old one was awful

the one thing is

in the new one

I can't create volumes

[ancient mango]

yes you can?

[proper bone]

how?

[ancient mango]

your two services already have volumes

[proper bone]

even when they didn't there wasn't an option

[ancient mango]

if there wasnt an option how did you end up adding the volumes

[proper bone]

what I did was create it in the "new project" and then create the template from there

[proper bone]

O, that should be added to the add service button as well

because you can do that in the project composer

they should probably just use the exact same component in both contexts

https://hedgedoc-production.up.railway.app/ does this look better to you?

[ancient mango]

it works!

[proper bone]

cool beans

the only thing is I'm not sure how to change capitalization in the template store

[ancient mango]

that would be done via the update button

[proper bone]

where?

and how do I change the description

[ancient mango]

also the update button

[proper bone]

Oh, this is another UX hard edge I think because there is also this

[ancient mango]

well the buttons do very different things

[proper bone]

and there's an update button here

[proper bone]

yes they do, but the update button should also be in the hamburger at the very least

and likewise, inside the composer, this button should take you to the edit panel you see when publishing a new template

[ancient mango]

that button edits the name lol

[proper bone]

Yes, it should bring up the edit sorry update menu instead

or there should be a button to do so in the composer

but that would get confusing

[ancient mango]

i think its pretty straight forward how it is right now tbh

[proper bone]

this is the menu I'm talking about btw

[ancient mango]

yes i know

[proper bone]

I'm simply stating that this is very clearly a UX difficulty I just experienced. If the railway team considers this difficulty to be a skill issue on my part, that's fine

obviously at a certain point of idiocracy you need to call it quits

[ancient mango]

i cant speak for the team, but i do

[proper bone]

but watching users try to do something and seeing their painpoints is very helpful

I love this video https://www.youtube.com/watch?v=QckIzHC99Xc

[ancient mango]

i do not have the attention span for a 24 minute video lol

[proper bone]

the part from 1:00 to 2:00 is most relevant

and then you can just skip to a random point to see painpoints she experiences

[ancient mango]

video from 2007 💀

[proper bone]

he basically tells her to do certain tasks and watches the ways she screws up doing said tasks

[proper bone]

"I don't know what an iPhone app is" quote from vid btw

[ancient mango]

so what i do every single day?

[proper bone]

right, but then the next step in UX testing is asking yourself if that painpoint can be reduced

which you cant because you don't work for railway

but railway should do this

[ancient mango]

i mean theres only so much you can do before the UI starts looking like a kids toy

[proper bone]

Sure. There's a balance before you start pandering to idiots.

[ancient mango]

you get it 😉

[proper bone]

Say with this. I thought there was a cache on these error messages. You told me that the routing tables needs to be updated. If I was a programmer working at railway, I would think "Ok, nothing here... yet" does not convey that something will be here soon clear enough. We should add subtext that says "Please wait a few moments for routing tables to update"

because I guarantee you if you asked 100 new users what this means, nobody would guess it means routing tables are updating and no action is required on your part

[ancient mango]

... yet should give you a good idea

i could ask 1000 users what a service is and they wouldnt know what it is

[proper bone]

I just asked a community of programmers, I've gotten one response so far

[ancient mango]

what are they even talking about though? did you even mention php?

[proper bone]

No. the intent is to ask a general community of programmers what this page means to them in a deployment context

because to me it looks like a 404 page

[ancient mango]

probably a good time to mention this, the nothing here yet page is not going to exist forever, at some point railway will roll out a change and you will never have to wait for such things

[proper bone]

Right. I get it. I'm just saying that ambiguities impact a great number of professional programmers. If a number of users ask the same question, it is possibly a UX issue

which they do, fwiw

[ancient mango]

impatient

[proper bone]

I mean, I guess?