Running on Saturn Cloud

[djdarlo]

Does anyone know if this is possible to run on Saturn Cloud - I was thinking for people without RPIs, this would be a neat solution.

https://app.community.saturnenterprise.io/auth/login

They offer servers with Python images.

[danmed]

Seems like a very expensive service.. a $1 vps from racknerd would handle it with ease..

[djdarlo]

I'm just looking for instructions on how to get the code across from github to the server and then execute it. Struggling at step 1 I'm afraid :(

…

On Fri, 14 Feb 2025 at 08:35, danmed ***@***.***> wrote: Seems like a very expensive service.. a $1 vps from racknerd would handle it with ease.. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5PC2G6SBHOTRHUPR2GHJ32PWTEFAVCNFSM6AAAAABXD57JYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJYGYYDCNBSHE> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: danmed]*danmed* left a comment (eelmafia/octopus-minmax#28) <#28 (comment)> Seems like a very expensive service.. a $1 vps from racknerd would handle it with ease.. — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5PC2G6SBHOTRHUPR2GHJ32PWTEFAVCNFSM6AAAAABXD57JYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJYGYYDCNBSHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[joeShuff]

There is a github action that you can have running for you, which is essentially free hosting.

It's the .github/workflows/daily.yml.disabled file.

If you fork this repo, then remove the .disabled from the filename you can run it in your own fork I believe. Unfortunately that will involve some git knowledge and github for setting up the action.

[eelmafia]

@djdarlo Are you not able to git clone the repository on the server? After that you just need to follow tutorials on how to install docker and docker compose and just use the command from the README.

[djdarlo]

Thank you. I think I've got it running now on a VM in GCP. I have populated the config file then tried running using the below command.

sudo docker run -d --name MinMaxOctopusBot eelmafia/octopus-minmax-bot

I'm not getting any output though.

Here's my config file....

services:
minmax_octopus_bot:
container_name: MinMaxOctopusBot
image: eelmafia/octopus-minmax-bot
restart: unless-stopped
environment:
- ACC_NUMBER=A-AEXXXXXXXX
- API_KEY=sk_live_XXXXXXXX
- OCTOPUS_LOGIN_EMAIL=[email protected]
- OCTOPUS_LOGIN_PASSWD=XXXXXX
- DISCORD_WEBHOOK=https://discord.com/api/webhooks/XXXXXXX
- ONE_OFF=true
- DRY_RUN=true
- PYTHONUNBUFFERED=1

Am I missing anything?

[adegartland]

I'm new to docker so take what I'm saying with a pinch of salt.

I think you've used the docker-compose config, but not use docker-compose to start, so you're effectively running with no config

You might have crud running forever in a container so to remove that do:

sudo docker container ls
then if you still see the old stuff running then
sudo docker stop MinMaxOctopusBot
sudo docker container prune

This is what I have for foreground dry run...

create a file env.sh:
----8<-----
#!/bin/s

Add your stuff here

export API_KEY=sk_live_xxxxxxxx

Your Octopus Energy account number. Starts with A-

export ACC_NUMBER=A-xxxxxxxx

export DISCORD_WEBHOOK=https://discord.com/api/webhooks/xxxxxx

export OCTOPUS_LOGIN_EMAIL=xxxxx
export OCTOPUS_LOGIN_PASSWD=xxxx

Whether to just run immediately and exit

export ONE_OFF=True

Don't actually make the switch, just show the prices

export DRY_RUN=True
-----------8<-----------------

create a file: run_docker_fg.sh
----8<-----
#!/bin/sh
. ./env.sh

docker run --rm --init
--name MinMaxOctopusBot
-e ACC_NUMBER="$ACC_NUMBER"
-e API_KEY="$API_KEY"
-e OCTOPUS_LOGIN_EMAIL="$OCTOPUS_LOGIN_EMAIL"
-e OCTOPUS_LOGIN_PASSWD="$OCTOPUS_LOGIN_PASSWD"
-e EXECUTION_TIME="23:00"
-e DRY_RUN="$DRY_RUN"
-e ONE_OFF="$ONE_OFF"
-e PYTHONUNBUFFERED=1
octopus-minmax-bot
----8<-----
chmod 755 run_docker_fg.sh
sudo ./run_docker_fg.sh

You could just get rid of the env.sh if you like and have it all the the same file, but I share the same config with background running variants...

Note, the "docker run" args are different. "--rm" auto prunes (so you can run the command immediately again) "--init" attaches an init process which so signal handling works better, "-d" is removed as you want to run it in the foreground, not as a daemon

[djdarlo]

Thank-you - I think I have it up and running in DRY RUN mode now :) Ended up running it on a GCP ubuntu VM. I've started the process using sudo docker-compose up -d and it's scheduled for 11pm tonight. I've also scheduled the VM to power down apart from 22:50 to 23:10 every day so I need to check that the power down/up doesn't interrupt the docker container. I'm very new to all of this but enjoying the learning curve.

…

On Fri, 14 Feb 2025 at 22:06, adegartland ***@***.***> wrote: I'm new to docker so take what I'm saying with a pinch of salt. I think you've used the docker-compose config, but not use docker-compose to start, so you're effectively running with no config You might have crud running forever in a container so to remove that do: sudo docker container ls then if you still see the old stuff running then sudo docker stop MinMaxOctopusBot sudo docker container prune This is what I have for foreground dry run... create a file env.sh: ----8<----- #!/bin/s Add your stuff here export API_KEY=sk_live_xxxxxxxx Your Octopus Energy account number. Starts with A- export ACC_NUMBER=A-xxxxxxxx export DISCORD_WEBHOOK=https://discord.com/api/webhooks/xxxxxx export OCTOPUS_LOGIN_EMAIL=xxxxx export OCTOPUS_LOGIN_PASSWD=xxxx Whether to just run immediately and exit export ONE_OFF=True Don't actually make the switch, just show the prices export DRY_RUN=True -----------8<----------------- create a file: run_docker_fg.sh ----8<----- #!/bin/sh . ./env.sh docker run --rm --init --name MinMaxOctopusBot -e ACC_NUMBER="$ACC_NUMBER" -e API_KEY="$API_KEY" -e OCTOPUS_LOGIN_EMAIL="$OCTOPUS_LOGIN_EMAIL" -e OCTOPUS_LOGIN_PASSWD="$OCTOPUS_LOGIN_PASSWD" -e EXECUTION_TIME="23:00" -e DRY_RUN="$DRY_RUN" -e ONE_OFF="$ONE_OFF" -e PYTHONUNBUFFERED=1 octopus-minmax-bot ----8<----- chmod 755 run_docker_fg.sh sudo ./run_docker_fg.sh You could just get rid of the env.sh if you like and have it all the the same file, but I share the same config with background running variants... Note, the "docker run" args are different. "--rm" auto prunes (so you can run the command immediately again) "--init" attaches an init process which so signal handling works better, "-d" is removed as you want to run it in the foreground, not as a daemon — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5PC2AVM6WQMPPDH4H6BLD2PZSHVAVCNFSM6AAAAABXD57JYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGM2TQNBTGE> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: adegartland]*adegartland* left a comment (eelmafia/octopus-minmax#28) <#28 (comment)> I'm new to docker so take what I'm saying with a pinch of salt. I think you've used the docker-compose config, but not use docker-compose to start, so you're effectively running with no config You might have crud running forever in a container so to remove that do: sudo docker container ls then if you still see the old stuff running then sudo docker stop MinMaxOctopusBot sudo docker container prune This is what I have for foreground dry run... create a file env.sh: ----8<----- #!/bin/s Add your stuff here export API_KEY=sk_live_xxxxxxxx Your Octopus Energy account number. Starts with A- export ACC_NUMBER=A-xxxxxxxx export DISCORD_WEBHOOK=https://discord.com/api/webhooks/xxxxxx export OCTOPUS_LOGIN_EMAIL=xxxxx export OCTOPUS_LOGIN_PASSWD=xxxx Whether to just run immediately and exit export ONE_OFF=True Don't actually make the switch, just show the prices export DRY_RUN=True -----------8<----------------- create a file: run_docker_fg.sh ----8<----- #!/bin/sh . ./env.sh docker run --rm --init --name MinMaxOctopusBot -e ACC_NUMBER="$ACC_NUMBER" -e API_KEY="$API_KEY" -e OCTOPUS_LOGIN_EMAIL="$OCTOPUS_LOGIN_EMAIL" -e OCTOPUS_LOGIN_PASSWD="$OCTOPUS_LOGIN_PASSWD" -e EXECUTION_TIME="23:00" -e DRY_RUN="$DRY_RUN" -e ONE_OFF="$ONE_OFF" -e PYTHONUNBUFFERED=1 octopus-minmax-bot ----8<----- chmod 755 run_docker_fg.sh sudo ./run_docker_fg.sh You could just get rid of the env.sh if you like and have it all the the same file, but I share the same config with background running variants... Note, the "docker run" args are different. "--rm" auto prunes (so you can run the command immediately again) "--init" attaches an init process which so signal handling works better, "-d" is removed as you want to run it in the foreground, not as a daemon — Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5PC2AVM6WQMPPDH4H6BLD2PZSHVAVCNFSM6AAAAABXD57JYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRQGM2TQNBTGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>