This is so specialized, I really can't think of a use for this other than for the one who wrote it.
Thanks for sharing though, it's always interesting to me to get to know the workflows of other people!
Show HN: Useful scripts and environment setup for coding in VPS
11–20 of 31 posts
Re: Show HN: Useful scripts and environment setup for coding in VPS
#12This is so specialized, I really can't think of a use for this other than for the one who wrote it. Thanks for sharing though, it's always interesting to me to get to know the workflows of other people!
Thank you, you're welcome :) I think you can use it as a base. Well maybe not you specifically, but someone can customize this... The git commands in particular save me lots of time, and I guess the rest is stuff used enough times i put it here to not have to look it up next time.
Re: Show HN: Useful scripts and environment setup for coding in VPS
#13I’d love to hear more specifics about what kind work you do. I saw Node, so I’m guessing backend Node development? Do you do front end too? If so, what’s your workflow for running a dev web server and accessing it from a browser?
Re: Show HN: Useful scripts and environment setup for coding in VPS
#14For the last couple of days, I've been trying to get a static website up using hugo (emacs + ox-hugo), and I've been using tramp to ssh into the machine and do my work.
Tramp is literally magic. It just puts the right text into your buffer, where all the tools you use on your machine are just available by default. Even org exports and the like behave as expected, outputting the resultant file into the correct dir on the remote machine.
I've been using emacs as a <50IQ user for about a year now. I've yet to write a single line of Elisp (apart from use-package declarations). It's awesome!
Re: Show HN: Useful scripts and environment setup for coding in VPS
#15I use something similar to configure my entire desktop from a default Debian install using idempotent shell scripts. The repo isn't public since it contains a lot of sensitive information but I'm currently developing something based on that for a server I'm working on: https://github.com/T0astBread/easymark-server-config
Re: Show HN: Useful scripts and environment setup for coding in VPS
#16I’d love to hear more specifics about what kind work you do. I saw Node, so I’m guessing backend Node development? Do you do front end too? If so, what’s your workflow for running a dev web server and accessing it from a browser?
Thanks Roben! :) Yes full stack, and the way I run most dev is to run it in the same server as production, but in another clone of the repo in a different directory, a different branch, and a dev port, like 6667. But keep the same certs TLS, and create a clone or dev version of the db. Then just access the same as normal but on the other port.
Occasionally, for like a larger project with load balancers, I'll run an entire dev single VPS with a subdomain of the production and use a wildcard TLS cert.
Then I can do whatever I like to the dev and production will be fine. Depending on situation, I might set it up blue-green and shift some traffic over from production and monitor and if it's ok, I push that to production. Or for larger projects, mirror the whole stack (two instance pools) and alternate production and dev, so I get continuous monitoring of the latest changes and I can roll back to the last stable version by traffic shifting if need be.
Re: Show HN: Useful scripts and environment setup for coding in VPS
#17I use something similar to configure my entire desktop from a default Debian install using idempotent shell scripts. The repo isn't public since it contains a lot of sensitive information but I'm currently developing something based on that for a server I'm working on: https://github.com/T0astBread/easymark-server-config
I wonder if you could do the same with Ansible ?
Re: Show HN: Useful scripts and environment setup for coding in VPS
#18> # uncomment for a colored prompt, if the terminal has the capability; turned off by default to not distract the user: the focus in a terminal window should be on the output of commands, not on the prompt :eyeroll: What a horrible attitude. The point of coloring is precisely to help users focus on the output that matters , rather than forcing them to parse and reparse a chunk of stuff they don't care about. If the p…
Ok, I think I copied that from somewhere... Pretty sure it's not my comment. But still... Lecturing people with rubbish arguments and a horrible attitude sounds like what you're doing. Big world out there. You can have people who like colors and those who don't. Neither have to be pretending they're all that and hate the other. :) Friends? Please submit a PR with a better comment if you like. I honestly didn't think…
I'm nearly certain that is a default message included in a lot of .bashrc files. I've seen it on Debian and Ubuntu. I agree with his criticism but certainly not with how he conveyed it. I love colour :)
Re: Show HN: Useful scripts and environment setup for coding in VPS
#19I use something similar to configure my entire desktop from a default Debian install using idempotent shell scripts. The repo isn't public since it contains a lot of sensitive information but I'm currently developing something based on that for a server I'm working on: https://github.com/T0astBread/easymark-server-config
Cool, yeah when you do it enough times you just want to script it. I use to have more sensitive stuff in here I think before I obliterated the historical stuff and made it a public repo, but I factored all that before sharing it. Like 2 years ago. It was a good exercise I think, separating secrets from config.
Re: Show HN: Useful scripts and environment setup for coding in VPS
#20> # uncomment for a colored prompt, if the terminal has the capability; turned off by default to not distract the user: the focus in a terminal window should be on the output of commands, not on the prompt :eyeroll: What a horrible attitude. The point of coloring is precisely to help users focus on the output that matters , rather than forcing them to parse and reparse a chunk of stuff they don't care about. If the p…
Ok, I think I copied that from somewhere... Pretty sure it's not my comment. But still... Lecturing people with rubbish arguments and a horrible attitude sounds like what you're doing. Big world out there. You can have people who like colors and those who don't. Neither have to be pretending they're all that and hate the other. :) Friends? Please submit a PR with a better comment if you like. I honestly didn't think…
Oh, I wasn't faulting you, most of these comments in rc files typically come all the way from some random flame in 1998 or something.
> You can have people who like colors and those who don't.
I absolutely agree, which is why I'd remove any opinion from the comment. "Default is off". End of story.