Then just enter the app name in the template as below.Read More Path('post//', post_detail, name='post_detail'),
Basically what you do is download ubuntu, then meteor and above puts node:8-alpine.ĭear Vitor,I believe the way to solve the problem is to add the app name in the file urls.py, leaving it as below:from django.urls import path, includeįrom. The bad thing is it depends on, and looking at it you see it depends on ubuntu, so we're talking about 1.07GB. to make meteor 1.8.1 with node 8, although it is intended to run it directly at the root of a project. If we do the exercise with the image node:8-slim, which occupies debian stretch (it's older, but if we're going to use node 8 I guess obsolescence gives a little the same) usando-nodeslim latest 63f47668aec5 827MB The result would be: usando-node-buster latest fbec649fea7a 836MB If you were to use for example buster in its slim version, you'd save so much dependency: FROM node:8-buster-slimĮdit do not need to install bash or curl in this image Now, let's think that by adding all the dependencies to be able to compile meteor, Alpine's liviandad is lost. Python2 make gcc g++ libgcc linux-headersĮNV METEOR_ALLOW_SUPERUSER true Install METEOR
RUN apk add ca-certificates openssl ncurses coreutils Second If you already have an image with node 8.16, you could skip the use of nvm and do: FROM node:8-alpine3.9 Where you install meteor, this won't work: RUN curl "$" | bashīut back to the subsection. To deal with the above, you can use an alpine image that already brings node 8 (but it's 8.16.2 today) FROM node:8-alpine3.9 Node 8.15.1 is actually installed, but it will claim you: env: ‘node’: No such file or directory If you do that, then you run something like what you have: RUN curl | bash \ Python2 make gcc g++ libgcc linux-headers \ Underground RUN apk -no-cache add curl RUN apk add ca-certificates openssl ncurses coreutils \ To run things like that curl | bash You have to install a few units. This makes binary programs built for such mainstream/traditional incompatible with Alpine Linux, thus we cannot simply nvm install X on Alpine Linux and expect the downloaded binary to run correctly - you'll likely see ".does not exist" errors if you try that. Mainstream/traditional Linux distributions - musl. (and thus Alpine Linux) use a different C/C++ stack to most But assuming it is, the first problem is to use alpine.Īlpine Linux, unlike mainstream/traditional Linux distributions, isīased on BusyBox, a very compact (~5MB) Linux distribution. I'm not sure if you specifically need version 8.15.