I tried xonsh, and I loved the few things I could do with it. But I work on Windows, where some of the shortcuts don’t work and if you press the wrong key, for example any arrow key, the terminal gets corrupted and, if you keep working without seeing what you do, it crashes after a few commands.
I first failed to configure neovim, now xonsh.
Linux is creeping more and more inside Windows with wsl2, but my Python environments interact with Excel and other software via COM, so I can’t jump the fence.
Why? I’m finding the cloud-UI development experience to be a bit nervous for my tastes and, as well, prefer to signal changes via vim(1)'s <ESC> :w! (not automatically saved by the UI). And other oddities.
So,…
Can I use amoni to perform most (or as much as possible) of my development coding locally (frontend, backend, Data Tables, with auto-completes, etc), and then be able to upload final assets to anvil.works cloud servers once complete?
This is my first Anvil.Works app, so it wouldn’t depend on any existing app on the cloud.
Note: I have one amoni environment running on my PC (per these instructions)
Is what I’m describing possible with amoni? Thank you.
I see. I missed that part of the Anvil documentation, but found it after you mentioned “Git” above. (Thank you).
Not having cloned any yet (I’m currently on the road), besides pushing changes back to Anvil frequently - perhaps to economize on successive pushes - can amoni be used to preview changes locally (mimicking how the App would ultimately appear on Anvil), and then a “mega push” be performed, say at end of day (or whatever)?
How might the setup sequence for that go:
git(1) clone […] MyAnvilApp
cd ./MyAnvilApp
amoni(1) init
Well, probably not exactly the nesting I created, but you probably understand what I’m driving at… How to integrate amoni with a git cloned Anvil App.
Down the road perhaps I’ll contribute a podman-config.yaml(5) file. I don’t install docker-ce by default anymore because I use podman(1) atop Fedora (a drop-in replacement for docker(1), but sans a daemon).
Copying docker-config.yaml(5) to podman-config.yaml(5) may work without change depending on it’s structure, but may need a little tweaking. I’ve had to do that occasionally.
An any case, I look forward to app cloning and development atop the local amoni stack.
Yeah, things happen so darn quickly in our Zeitgeist. When I’m in MS-Windows these days, I notice the development differences less and less (once wsl2 is running). RedHat/Fedora (the creator of Podman) helped with the integration, and have been really pushing boundaries. Fedora, for example, has the Immutable filesystem but much more, too. This was off-topic, but figured I’d offer the contribution.
Back to the thread subject, later today I’m going to start a fresh App, git clone it, then try to determine how to get it to run atop amoni (I’m still unsure how to, but I haven’t tried anything yet ).