You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
just wanted to ask if you could explain the basic functions of every file that is included in every OS directory in the readme to make the contribution easier?
I saw that Parallels and VMWare Fusion Beta are the available platforms for macOS on M1/ARM. Is there a reason, besides effort, not to support both?
Is there a chance to create an automatic build pipeline, so shipping updates will be easier or does the image build need a mac and the specific virtualization platform itself?
Hope I can contribute and help
Simon
The text was updated successfully, but these errors were encountered:
This will be added to https://github.com/BytesGuy/arm-base-boxes#usage-instructions in due course. The repo needs refactoring to make it easier to follow before I add that, but generally everything included is fairly standard packer + some scripts for automating cleanup of the vm and packaging into the vagrant box
Parallels is starting to be added, I only have a trial license though so I am not sure how much support I will be adding moving forward as it is £80/year and I work solely with VMWare in other activities
Ideally yes, I work at CircleCI so I would use that, but due to this requiring a Mac with virtualisation enabled (so can't use a VM) and VMWare and/or parallels installed, that would mean it would need to use a custom host machine with CircleCI Runner for best results. A weekly update cadence for package/security updates would be the best scenario. I'll see how it goes moving forward
Hi @BytesGuy,
just wanted to ask if you could explain the basic functions of every file that is included in every OS directory in the readme to make the contribution easier?
I saw that Parallels and VMWare Fusion Beta are the available platforms for macOS on M1/ARM. Is there a reason, besides effort, not to support both?
Is there a chance to create an automatic build pipeline, so shipping updates will be easier or does the image build need a mac and the specific virtualization platform itself?
Hope I can contribute and help
Simon
The text was updated successfully, but these errors were encountered: