Shipping a Café Menu in a Container is a hands-on DevOps project for beginners with basic terminal familiarity. Take LITTLE HOUR's complete café website to a fresh running container, including its drink details, illustrations, prices, and opening hours. The application is supplied; your work is to package and deliver it.
One Guided Lab introduces the Dockerfile, build context, image, container, published port, and the checks that distinguish a complete delivery from a working homepage. One independent Challenge gives you DAYBREAK's bakery menu with pages, styles and pictures in separate source directories. Each unit starts in its own prepared environment.
What You Will Learn
- distinguish an image from a running container;
- package customer pages and local design assets with explicit COPY destinations;
- keep author-only drafts out of a public website;
- build a named image and publish its server through a container port;
- start a fresh container without host-directory mounts and check real customer paths.
Who This Course Is For
This course is for DevOps beginners, new developers and anyone curious about delivering a small website with containers.
Prerequisites: You should be comfortable entering terminal commands and recognizing paths. No Docker, Nginx administration, programming or website-building experience is required. The necessary concepts, command options and shell syntax are explained before use.
Learning environment: LabEx supplies a browser-based Linux workstation with Docker, a prepared Nginx base image, complete website files, a design reference and your own website tab. There is no local setup or external account. The synthetic storefronts accept no real orders. The websites, tab labels and command output are in English.
Frequently Asked Questions
Will I build a website or write application code?
No. The complete websites are provided. You write a short Dockerfile and use terminal commands to build, run and inspect the delivery.
How is the Challenge different from the Guided Lab?
The bakery's pages, stylesheet and illustrations have separate source locations. You decide how to assemble the complete public site using the same COPY and container methods already practiced. A full explanatory solution is available.
Does a running container mean the delivery is complete?
No. The detail pages, pictures, styles and visit information must actually work without source mounts, while author drafts remain unpublished. The course checks real artifacts and responses, without requiring a report.
Does this cover a full production container platform?
The focus is packaging and independently running a static website. Registries, orchestration, persistent databases, TLS and production operations are outside this short project.
