The config.json should be switched in exchange for the repl.it SECRETS, so nobody can just nab your auth key and token and make themselves a high rank
1 Like
Yeah, but it is hard to find the project unless you publish it to the template gallery.
Storing your key in .Json means your allowing people that will fork your code, will see the Json file containing the token, you should probably change it to .env instead. Or as .env is deprecated, use the repl it secrets thing
2 Likes
You can just rename the file to .env or just go to replit secrets and put the token there
1 Like
you use the ‘secrets’ tab in repl
1 Like
oh didn’t know that. thx for the info
2 Likes
Anyone got the stuff working? 
You can access secrets by doing process.env.yourenvkeyname
Correct. It’s useless to have a json if you are storing secrets.
1 Like
Well, did it work? I’m curious 
i’ve never used replit, thats just what i heard
Ah, you should. It’s really cool 
the only thing is, they can fork my repl, maybe ill use it one day for some proxy but im pretty sure ill suck at other programming languages
thus they dont allow 24/7 hosting unless you pay them
Nope. They cannot find it unless they Google the exact URL in the search bar up, it will not be searchable like glitch, and your cookie will be hidden in the .env
Use uptimerobot, you’ll get 24/7 hosting with replit.
okay, sure i can get 24/7 hosting and its difficult to fork repl’s, however i suck at other languages ( dont get me started at java)
1 Like
No, everything is listed here, and it’s JavaScript.
Just use the free resources I’ve programmed
1 Like