# Frequently Asked Questions ## Can you access ".." with go-live? When the go-live process starts, it serves all files and sub-directories that the user has read access to. Any files or directories above the target directory aren't served by the process, that includes ".." ## What is the difference between go-live and Javascript's live-server? The famous Javascript package, live-server () inspired the go-live project. However there are some major differences: * live-server is designed exclusively for local development, go-live is designed both for local development and production file serving. * live-server requires Node.js be installed on a system. Because Go is compiled, go-live can be deployed on any system or architecture that Go supports. * live-server requires over 52 MB of NPM modules, and Node.js (another 30MB) to be installed, go-live is around 5 MB for an entirely self-contained executable. * go-live supports sharing files on the subnet or internet via a light-weight file server. ## --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://antsankov.gitbook.io/go-live/misc/faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.