Wauw looks good!

Hello good morning, this great what you created, you could add the protection of requests with the token that is generated, currently you have the requests open to all and cuaquier person can make records.

I look forward to your reply, thank you.

Hello good morning, this great what you created, you could add the protection of requests with the token that is generated, currently you have the requests open to all and cuaquier person can make records.

I look forward to your reply, thank you.

I appreciate your suggestion, when I added that key I thought about this feature, but I did not have time. However today I could take some time to implement this feature, and now it's on flight, every request must have a header with a token field that includes the generated key. To avoid break changes, I added an environment variable that allows bypassing the auth process while not upgrading current clients, but this will be temporarily soon it will be mandatory.

Thank you for your time and work on this template, looks like the community is finding good uses for it!

I have some feedback that could improve the template's DX -

• Use a reference variable for the redis url variable so users don't have to deploy and figure that out after the fact.

  https://docs.railway.app/guides/variables#referencing-another-services-variable

  You would want to reference the private url variable on the redis service.

• Use template variable functions to auto generate an auth token so your template users aren't deploying all with the same initial auth token.

  https://docs.railway.app/guides/create#template-variable-functions

Sorry for the delay brody, I appreciate your templates. About the topics you suggested, I kept them in mind and set up both, and now it's much better to configure the template and make it easier to set up and deploy. Thank you for your time.

Hi good morning, I was testing your new changes and I noticed that it is not documented all the functions. it would be great if you add it with swagger so I can access it through a route.

I have this is mind to be done. I will soon do a refactor in the project and I definetely will add more documentation and swagger endpoint. Keep an eye in it