A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
Thank you! This article is awesome!
I was so inspired by the technique you describe that I created a new project, glitcheroo. It lets you deploy an app from a local git repository to a remote Glitch project, kind of like Heroku.
Whoa, I'm totally gonna check this out, it sounds awesome.
I wrote up an introduction here: dev.to/bacongravy/introducing-glit...
I'd love your feedback.
Reading now + sharing with my colleagues!
Coming full circle, I also created a project to demonstrate how to use glitcheroo from a GitHub Actions workflow: github.com/bacongravy/useful-insect
glitcheroo
This is the interesting part:
- name: Deploy project to Glitch run: | npx glitcheroo deploy env: GLITCHEROO_GIT_URL: ${{ secrets.GLITCHEROO_GIT_URL }}
because i couldn't change the repo i want to deploy with your tool i used the guide above to change the soure_branch to the branch i want to deploy
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you! This article is awesome!
I was so inspired by the technique you describe that I created a new project, glitcheroo. It lets you deploy an app from a local git repository to a remote Glitch project, kind of like Heroku.
Whoa, I'm totally gonna check this out, it sounds awesome.
I wrote up an introduction here: dev.to/bacongravy/introducing-glit...
I'd love your feedback.
Reading now + sharing with my colleagues!
Coming full circle, I also created a project to demonstrate how to use
glitcheroofrom a GitHub Actions workflow: github.com/bacongravy/useful-insectThis is the interesting part:
because i couldn't change the repo i want to deploy with your tool i used the guide above to change the soure_branch to the branch i want to deploy