This commit is contained in:
kn0wmad
2021-12-07 20:30:40 -07:00
committed by Lucy Cifferello
parent ff5871dd9a
commit 77439ce07f
4 changed files with 39 additions and 17 deletions

View File

@@ -4,8 +4,28 @@
Service Packaging FAQ
*********************
Do I need programming experience to package a service for EmbassyOS?
--------------------------------------------------------------------
It would be helpful, but is not a pre-requisite. Linux, dev-ops, and/or systems administration experience would all be helpful as well. Keep in mind that everyone has to start somewhere, and perhaps your journey to development begins with packaging a service for EOS!
What considerations are there when choosing a service for packaging?
--------------------------------------------------------------------
There are several things you will want to consider. Requirements include:
#. Most importantly, pick a service you are passionate about seeing on EmbassyOS.
#. Make sure it is :ref:`Open Source <open-source>`
Recommendations that may ease the process:
#. A service that has already been 'dockerized' (has a **working** ``Dockerfile``)
#. A service written in a language you are familiar with
#. A service with a strong community
What if I don't need a Config in my service?
--------------------------------------------
Config files can be empty(``{}``), if you do not require config.
How can my service access the data directory of another service?
----------------------------------------------------------------
1. Provider service needs to expose datadir to other services on embassy
2. Consumer services needs to list the provider service as a dependency AND set a particular config value, stating that it wants data from that particular service
#. Provider service needs to expose datadir to other services on embassy
#. Consumer services needs to list the provider service as a dependency AND set a particular config value, stating that it wants data from that particular service