1,029 reputation
1821
bio website twitter.com/jjmontes
location Spain
age
visits member for 4 years, 1 month
seen Mar 16 at 19:13

Computer Science Enthusiast!


Mar
4
awarded  Famous Question
Feb
27
awarded  Autobiographer
Feb
8
awarded  Yearling
Nov
28
awarded  Caucus
Nov
28
awarded  Constituent
Oct
29
awarded  Nice Answer
Oct
24
awarded  Critic
Oct
24
comment API and main page as two separated processes
Added to the response. This thread is now getting too long. Rather, ask new questions ;-). Hope it helps.
Oct
24
revised API and main page as two separated processes
Added info about building URL patterns.
Oct
24
comment Linux router - how to send icmp unreachable messages to LAN clients
The reject target will by default send a port-unreachable, for the described use case it may be advisable to use reject --reject-with icmp-net-prohibited or icmp-net-unreachable?
Oct
24
comment API and main page as two separated processes
Yes. Also note you can also include one or other URLs conditionally, depending on the availability of the module or depending on some setting, or simply have separate main urls.py. It's more of a matter of taste or final application (ie. if you need people to enable or disable functionality from config -> then use a custom setting and conditional logic in your main urls.py).
Oct
24
comment API and main page as two separated processes
Yes, you can do that. For URLs, you can also point your settings.py to different urls.py, which then include the appropriate urls.py from subapplications (remember you can and should have a urls.py on each application, including with ie. url(r'^api/1.0/', include('myapi.urls', namespace='myapi'))). For organisation, I usually keep api URLS within "/api/" which doesn't conflict with website or other apps, even if they are deployed in the same process. I hope to have made sense here...
Oct
24
awarded  Citizen Patrol
Oct
24
awarded  Informed
Oct
24
answered API and main page as two separated processes
Oct
23
answered (network unreachable) error in my server logs
Oct
23
comment Update ubuntu automatically
To me, it means that when you have testing environments, you shall apply upgrades only to testing/preproduction environments first, and then roll out to production. In practice, Ubuntu security updates are very stable, and it's very unlikely that they break anything, especially if you use a common stack of software (ie. LAMP).
Oct
22
awarded  Explainer
Oct
22
awarded  Organizer
Oct
22
revised Update ubuntu automatically
Added ubuntu tag, formatted messages and command lines.