Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable development with VSCode and Docker #92

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nznobody
Copy link
Contributor

@nznobody nznobody commented Aug 29, 2021

This is an initial attempt at adding Docker & VSCode workflows to enable desktop development. They have not yet been extensively tested and this PR is more to advertise the intent and gather feedback :)

@amotl
Copy link
Member

amotl commented Aug 30, 2021

Hi Manu,

thanks a stack for this excellent patch, we will be happy to accept it. As I am not a VSC user and don't use Docker for developing Terkin, maybe @poesel, @thiasB, @MKO1640, @ClemensGruber or @einsiedlerkrebs have something to add here.

Coming from [1], I see that you are into eagle.io [2], but you might still be interested into a full FOSS DAQ solution based on Kotori [3] and more, where we have a full Dockerized environment at [4], contributed by @WSt89 the other day. I brought this one up to speed just recently after it has been dormant for a while.

On the other hand, it would be very sweet to see a telemetry adapter for eagle.io based on your pyeagleio library [1] to be contributed to Terkin. Is this something you are aiming at?

In general, if you are interested about the development history of Terkin, you are welcome to join our forum and read some articles along [5]. Roughly, the development started being focused on MicroPython, but as you can see from [6,7], the environment has been expanded to CPython as well. If you have a hard time reading the forum discussions in German, you can use the translation button below each post after becoming a member.

With kind regards,
Andreas.

[1] https://github.com/nznobody/pyeagleio
[2] https://eagle.io/
[3] https://github.com/daq-tools/kotori
[4] https://github.com/hiveeyes/hiveeyes-backend-docker
[5] https://community.hiveeyes.org/tag/terkin
[6] https://community.hiveeyes.org/t/developing-terkin-for-cpython/4088
[7] https://community.hiveeyes.org/t/terkin-variante-fur-cpython-raspberry-pi-dragino-lora-gps-hat/3180

@amotl amotl changed the title Feature/docker workflows Enable development with VSCode and Docker Aug 30, 2021
@nznobody
Copy link
Contributor Author

Hi Andreas,

Thanks for the warm welcome! Much appreciated 😄

I have briefly looked into the Kotori stack you mentioned. It does look great indeed. I am, however, contributing to this mainly for my work in assisting our existing research, which uses Eagle.io and other systems already.

To add context (and get your thoughts) my research is focused on aquaculture and my plans were to extend and add drivers for common sensors used in that domain to this codebase. I would mostly run this variant of terkin on a combination of something like the Fipy, Raspberry Pis, and standard computers. Hence my interest in a Micropython / CPython cross implementation of a generic datalogging framework! Sensors would include:

  • YSI EXO: nznobody/pyserialdrivers (Will also migrate to pfrnz soon)
  • Nortek ADCP
  • Airmar Weather Stations
  • Other (Dissolved Oxygen, Temperature, turbidity,...)
    As these mostly operate at a higher level bus (serial) maybe this is not the right repository, but it is the best I have found. What do you think? Would I be wasting my efforts on this journey? I will watch the CPython development closely 😄

Yes my intention is to enable out-of-the-box eagleio support via pyeagleio. Note that I have moved that archive to a public repository on my work's enterprise account: pfrnz/pyeagleio
Additionally I have a python-to-micropython packaging script I am wanting to test to enable the inclusion of pyeagleio.

Regarding German, thanks! I have signed up for the forums. Luckily I am half German and can still somewhat read it which gets me by for now!

@nznobody
Copy link
Contributor Author

Update: I have since achieved eagle uploading via basic CSV. Due to the requirements of micropython that may be preferable for now.

I will still work on finishing this off and enabling dev, test, and build docker workflows.

…nt on any system (with docker)

VSCode development container

attempt to not mess with file endings

Allow running with debugging as module

Add docker workflow documentation start and VSCode remote container config

enable docker container development environment

split vscode image into seperate image

only start VSCode container for dev env
@nznobody nznobody force-pushed the feature/docker-workflows branch from 724953c to cd247a1 Compare October 13, 2021 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants