Will talk about Linux, plants, space, retro games, and anything else I find interesting.

Also mesa@piefed.social over on Piefed.

  • 63 Posts
  • 234 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle








  • mesa@lemmy.worldtoProgramming@programming.devGit without a forge
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    5 days ago

    The biggest thing git does is one person can get one or many branches (AKA version control) on ANY machine. They all act like they are the source of truth. CVS/Mercurial/etc…all have the issue that they expect to be on one machine as the source of truth. And if that machine ever goes down…

    Before git (ya im old), I used a plethora of services like git. There were times back then when a server was down and the history…was just gone.


  • mesa@lemmy.worldtoProgramming@programming.devGit without a forge
    link
    fedilink
    English
    arrow-up
    25
    ·
    edit-2
    5 days ago

    I worked at a place that just had a git on a sftp server and that was it. Worked well in a small team. Git is made for it.

    Having a separate issue tracker turned out to not be a big deal at all. Theres a lot of niceties github has, but it turns out you really dont need a whole bunch to make good software.

    Nowadays i would probably go with gitea or forgeo if I had to self host, but git by itself is perfectly fine.




  • mesa@lemmy.worldtoFediverse@lemmy.worldBotKit 0.2.0 released
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    6 days ago

    Interesting:

    BotKit is a TypeScript framework for creating standalone ActivityPub bots that can interact with Mastodon, Misskey, and other fediverse platforms without the constraints of these existing platforms.

    I wish more open source projects would tell you what the thing does haha.












  • Yep take a look, theres quite a few examples, but they use Github Actions, CircleCI, Gitlab etc… etc…

    Most CI/CD that use the above-ish model will use the same kinda scripts (bash or otherwise). Basically if you can do it on your desptop, you can automate it on a server. Make it work first, then try to make it better.

    Most of the time, ill throw my Docker/Docker Compose (and/or terraform if need be) on the root of the repo and do the same steps I do on the development side for building/testing on the CI side. Then switch over to CD with either a new machine (docker build/ compose) or throw it all on a new server. At that point, if you script it out correctly, it doesnt really matter what kind of server you use for CI/CD, since they are all linux boxes at the end of the day.

    You can also mix it up by using bare metal, docker alternatives, different password managers, QA tools, linters, etc…etc…

    But virtualization will get you quite far. In my opinion start with just trying to get the project to build on another server via a script from scratch, then transfer it over to the CI. Then go with testing/deployment.

    GL!