Hi Tim Here are my notes on installing Pharo in a DigitalOcean Ubuntu droplet. I usually go thru a Windows Command prompt box having installed xfec4 in the ubuntu droplet, but the command line connect and graphical remote may be easier for a Linux users. my ssh public key is also in the DO droplet Now the first step for me is a installing Pharo launcher thru command line and then everything is thru graphical interface
Installing and checking Pharo-Launcher, Installing Pharo 8 64 bit from pharo.org (instructions as on Pharo.org) 1. In Windows 10 command prompt connect thru > ssh root@<Droplet-ip> 2. cd 3. curl -o pharo-launcher.zip -L https://files.pharo.org/pharo-launcher/linux64 4. unzip pharo-launcher.zip or thru the GUI-> extract here (pharo-launcher files will be extracted in ./pharo-launcher) Now while connected to the linux graphical interface thru windows remote terminal and in the GUI 5. Create a icon on desktop thru right-click “Create Launcher” for pharo-launcher 6. Create pharo images thru pharo-launcher hope this is of use Sanjay Minni On Thu, 1 Apr 2021 at 16:31, Tim Mackinnon <tim@testit.works> wrote: > Hi everyone - its been a few year since I last hosted a little Pharo web > app - and the last time I did, Sven pointed me to DigitalOcean and creating > a tiny instance and configuring an Ubuntu server and then copying a pharo > image on to that. It recall it wasn’t too bad, albeit a bit fiddly… > > Now several years later - I can’t recall the exact steps, and vaguely > recall there was something about 32bit vs 64bit setup etc - but am > wondering if things have advanced a bit and whether its much simpler these > days? I’ve seen references to Docker images for Pharo, and am wondering if > now that is a prime time way to easily get a small demo application up and > running with minimal fuss. > > Does anyone have advice - or something to point me to? > > Ideally I want to hook something up in Gitlab CI do deploy to this thing > automatically (this is where I got to a few years ago - but in picking > things back up I am hoping this has all got much simpler). > > Tim