Comments (5)
Yes, good idea. I've added katon touch
in v0.6.4.
from katon.
What does it touch?
from katon.
touch ~/.katon/hosts/<app_name>.json
katon is monitoring these files and reloads server configuration. It should be noted though that the server is stopped and you need to make a request to get it started (same behavior as katon rm && katon add ...
)
from katon.
I see. In that case I would suggest picking a more appropriate name for this command, such as "restart" or "kill".
There are two common touch abstractions:
- The server is watching a file (e.g.
restart.txt
), the developer touches that file to restart the server - The developer's own code is watching files for changes (typically reload server), something else is expected to touch one of these files
Both are "touch" abstraction because you're expected to either touch a file, or write code that responses to a file that's touched. In both cases "touch" describes what it does.
In Katon's case, however, "touch" doesn't describe what it does, but how it does it. And that's why I think the name is inadequate. I care to know what the command does. Whether it uses file touching, or signals, or sockets, those are just implementation details.
You can tell when it's the right abstraction if the command name remains the same (e.g. katon kill
) even as the implementation changes from using one mechanism to another (e.g. from touch to signal).
As for what would be a better name, if I understand it correctly, this command effectively kills the server, so that would be the most appropriate name.
from katon.
On Mon, Oct 13, 2014 at 12:09 PM, Assaf Arkin [email protected]
wrote:
I see. In that case I would suggest picking a more appropriate name for
this command, such as "restart" or "kill".There are two common touch abstractions:
- The server is watching a file (e.g. restart.txt), the developer
touches that file to restart the server- The developer's own code is watching files for changes (typically
reload server), something else is expected to touch one of these filesBoth are "touch" abstraction because you're expected to either touch a
file, or write code that responses to a file that's touched. In both cases
"touch" describes what it does.In Katon's case, however, "touch" doesn't describe what it does, but how
it does it. And that's why I think the name is inadequate. I care to know
what the command does. Whether it uses file touching, or signals, or
sockets, those are just implementation details.You can tell when it's the right abstraction if the command name remains
the same (e.g. katon kill) even as the implementation changes from using
one mechanism to another (e.g. from touch to signal).As for what would be a better name, if I understand it correctly, this
command effectively kills the server, so that would be the most appropriate
name.—
Reply to this email directly or view it on GitHub
#39 (comment).
Adam Becker
510.928.9111
@AdamJacobBecker
from katon.
Related Issues (20)
- xip.io does not work? HOT 4
- Properly replace underscores with dashes when determining current app name HOT 1
- PHP Server Not Routing HOT 15
- Support websockets HOT 2
- Stop daemon after period of inactivity HOT 2
- Apache fighting with Katon HOT 10
- pause / resume commands HOT 1
- Security issue: binds to 0.0.0.0 by default rather than 127.0.0.1 HOT 2
- feature request: katon open w/ https instead of http HOT 3
- Rails: Command '--port' not recognized HOT 9
- Wrong log filename in error message HOT 1
- 0.10.2 doesn't include PRs 66 or 67 HOT 1
- *.xip.io links give connection refused HOT 1
- Using rails --port, katon listens on the port but doesn't forward traffic HOT 1
- Support ngrok domains
- Configure 4 second timeout on app load... HOT 4
- Xip.io resolution fails, have to reinstall katon now and then HOT 5
- Broken in OS X El Capitan HOT 6
- Support location (path) proxy routing HOT 3
- Forwarded HTTPS requests should set X-Forwarded-Proto HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from katon.