DEV Setup Question

whatthemeh

Anyone here setup a dev environment on a mac?

I had it all working but wanted to have Apache serve files from my potential dev directory instead of having the dev environment look to a share from the Parallels VM I setup and I get error 403.

Not really sure if the environment I have in my head is the best way to go about setting up one.

Before I go back to the initial setup I wanted to see if there was something I am missing or is truly the path of least resistance share html directory on the VM so that the mac can either edit files on the fly or copy changes to it.

macOS 15.1

m4 pro chip

Parallels Desktop 20

Debian 12.8 VM

Bigbug

whatthemeh

setup a Debian 12 VM (without GNOME/desktop environment - to make it lighter)
fork the ITFlow repo to your own GitHub account
Download the install script - wget https://github.com/itflow-org/itflow-install-script/raw/main/itflow_install.sh
Edit the script on line 224 and replace the git link with the git link of your fork
then run the script ./itflow_install.sh (you might have to edit permissions chmod +x itflow_install.sh )
you can use GitHub desktop to work on your Mac

and there you go!

whatthemeh

Bigbug so far so good thanks

whatthemeh

Thanks! I am gonna give this a shot and let you know.

wrongecho

Good advice from @Bigbug but I'll also drop a link to the docs too: https://docs.itflow.org/contribute

Note that we now use the develop branch as the active branch, so any PRs should be raised against there.

Bigbug

wrongecho Note that we now use the develop branch as the active branch

Just curious how often will the develop branch be merged into master?

because i think it could make some problems if there's too much updates at once, as we saw here from people that they didn't update their instance frequently enough and things went south

whatthemeh

wrongecho

Thanks for this as well. Glad you pointed out my reading comprehension/ lack of coffee and that i realized i cloned wrong branch

wrongecho

Bigbug

It'll be monthly-ish, the last release was 24.12 and the next will be 25.1.

It was a little crazy before as you could be having to update multiple times a day. Sometimes we'd be pushing slightly broken updates and then fixing them a few hours later.

Now it'll just be once (or potentially twice) a month and should be more stable in general. We've worked around much of the in-app update issues as we now have the update CLI script as a backup. It also simplifies the "what version are you running" troubleshooting when people are having issues as we have a proper version release number.