From Docker to Real Services: My Learning Journey with MyZubster

What happens when a software project becomes a place to share your practical skills?

I’m Nicola, also known as N4K48. Through my work with Daniel Ioni and MyZubster, I’ve been learning how to connect GitHub documentation, Docker, APIs, Zorgax and real community activities.

Now, two of my services are published on the MyZubster Marketplace.

🚚 Need help with a move?

I own a pickup with a tow hitch and hold B, C and CE driving licences, plus CQC goods qualification.

My listing covers small moves and bulky-item transport around Rimini. I’m also available as a driver when the customer already has a suitable vehicle.

Indicative driver rate: €20/hour. Pickup use, fuel, tolls and any trailer costs are agreed separately.

👉 Open the Marketplace

Look for:

“Traslochi e trasporto ingombranti — pickup e autista disponibile”

Then click “Richiedi” to make a request.

🧠 Want to learn from my driving experience?

My second service offers individual sessions to share practical experience with transport preparation, moving logistics and working as a driver.

Price: €20 for a one-hour session, in Rimini by appointment.

These are experience-sharing sessions; they do not include driving lessons, licence courses or certification.

👉 Find my knowledge service on MyZubster

Look for:

“Conoscenze pratiche da autista — patenti B, C, CE e CQC merci”

The Marketplace currently opens as a shared listing page, so these links do not jump directly to an individual service.

💻 What I learned while building

The practical work taught me lessons that go beyond publishing an announcement:

• Docker: a working command-line client does not mean the Docker engine is running.
• API testing: a healthy container does not guarantee that every endpoint works.
• Packaging: excluding runtime catalog files from a Docker image can break a feature.
• Bug reporting: the exact error message makes a failed test useful.
• Marketplace testing: currencies, prices and successful publication need checking.
• Zorgax: the comics adapter uses explicit catalog actions; its responses should remain tied to available records.

During the moving-service test, publication failed with:

E11000 duplicate key error
index: listingId_1
dup key: { listingId: null }

I reported that error and a missing EUR currency option to Daniel. After he reported deploying fixes, we repeated the flow and verified that the listings appeared.

That is the learning cycle I want to keep using:

Try → observe → report → fix → verify → share.

🥛 Where kefir fits in

The Kefir & Knowledge pilot connects a physical exchange with documentation and learning.

It also raises a useful engineering question: what does a digital record actually prove?

Delivery confirmation, receipt confirmation and a digital record are distinct steps. Scientific conclusions require their own observations, methods, data and review.

My GitHub journey includes a kefir illustration and diagrams explaining this pathway. They describe the project and its next steps, rather than presenting completed scientific results.

🔗 Choose your next step

💬 Help me test the experience

Open the Marketplace and try to find one of my listings.

Can you tell what the service includes, what it costs and how to request it?

Leave a comment with the step that felt clear—or the point where you got stuck. Please submit a service request only if you are interested; usability feedback can stay here in the comments.

And if you’re building something similar: what practical skill would you turn into a useful community service?