BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Container to deploy a web service
- Subject: [Discuss] Container to deploy a web service
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Thu, 8 Nov 2018 10:05:15 -0500
- In-reply-to: <CAJWk+TPWHP+FXBe01BOsX8qYDoByOqpid98+t2ZoGUe6HgFwZA@mail.gmail.com>
- References: <CAJWk+TPWHP+FXBe01BOsX8qYDoByOqpid98+t2ZoGUe6HgFwZA@mail.gmail.com>
On Thu, 8 Nov 2018 02:34:42 -0500 Tom Luo <mariolzx at gmail.com> wrote: > Basically, what I need is to provide a port for customers to access > the service. At the same time, I don't want customers to see my code. > > What should I do? Any ideas? The Docker host can see everything in the container. The customer controls the Docker host. Therefore the customer can see everything in the container. Likewise the VirtualBox host once the encrypted VM is unlocked. Likewise every other deployment where the customer controls the deployment target. Solution: If you don't want your customers to see the source code then don't ship source code. -- Rich Pieri
- Follow-Ups:
- [Discuss] Container to deploy a web service
- From: jay at lentecs.com (Jason Normand)
- [Discuss] Container to deploy a web service
- References:
- [Discuss] Container to deploy a web service
- From: mariolzx at gmail.com (Tom Luo)
- [Discuss] Container to deploy a web service
- Prev by Date: [Discuss] Container to deploy a web service
- Next by Date: [Discuss] Container to deploy a web service
- Previous by thread: [Discuss] Container to deploy a web service
- Next by thread: [Discuss] Container to deploy a web service
- Index(es):