Comments (5)
I guess that is why no practical example is given n README. it all sounds so nice - but breaks down in the real world of course like all webtech I've ever seen.
from seashells-server.
Live sessions are retained indefinitely. There is a 5 sessions/IP limit, and dead/completed sessions are GCed after 24 hours. There's also a limit on the number of bytes per session, and that data is stored in a circular buffer, so only the last N bytes are retained.
Unlimited retention is infeasible due to abuse. (There are already a lot of people occasionally running seashells < /dev/urandom
, sending me random bytes at 100 Mbit/sec)
Maybe this will become an option for non-anonymous users once we get a user account system.
from seashells-server.
I can understand the need to protect from abuse. Still if nothing happens soon I may face "investing" few weekends on writing an open-source server, to escape the limitations.
PS. I could guess that the reason for not having the sever open source would be that you may be interested to build a PaaS model. At the same time this means that you may miss a huge number of users and contributors (i know for sure a big number of users would not even try it just because they would do almost anything to avoid a vendor lock-in). Look at GitLab, is open source but people still pay for it (lots of other examples). People are likely to pay for the commodity of using a hosting service, especially when they know they could run their own service, if they are no longer pleased with TOS ;)
from seashells-server.
Live sessions are retained indefinitely. There is a 5 sessions/IP limit, and dead/completed sessions are GCed after 24 hours. There's also a limit on the number of bytes per session, and that data is stored in a circular buffer, so only the last N bytes are retained.
Hi, what do you mean here with "Live sessions" ?
I am having also the issue of a "sessions" expiring after some hours/days.
Should a "Live session" still be retained indefinitely?
What I do is the following:
while true ; do clear ; _some_command_ ; _some_other_command_ ; sleep 1m ; done | seashells -q -d 30 &
Should that output then be retained indefinitely?
Thanks,
Richard
from seashells-server.
It'll retain output as long as your TCP connection to Seashells isn't broken. Seashells isn't designed to store data long-term.
from seashells-server.
Related Issues (4)
- TLS HOT 1
- Re-use of URLs HOT 3
- `baseUrl` hard-coded to seashells.io 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 seashells-server.