I just moved away from a T3 line back to a dial up I just wanted to know would a P200 with 64meg and a 4 gig hard drive be ok for a linux server for an additional 3 pcs all running win98. I will be dialing into an isp using a 56k v90 modem.
Any support or help will be great. (3 Replies)
Hello all
this is general question , if i have web server installed in my local pc and i have client that connecting to that web server
can i force it always to go via the internet network ?
the reason im asking is .. that im noticed when i close my internet connection i still can connect to my... (2 Replies)
hi i have linux server connected to internet through a switch/router. i have opened a port on the router and i am able to connect to the server if iptables is off. but when it is on i cant.
i want to create a rule in iptables so that it accepts packets coming from a particular datacard. it... (7 Replies)
In my further exploration of Arduino, today I decided to install the arduino-cli on my mac today.
https://github.com/arduino/arduino-cli
I followed the instructions for macOS but when I got to this part:
arduino-cli board list
I got the dreaded "Unknown" Fully Qualified Board Name... (1 Reply)
My favorite projects are always related to the "latest" tech in command and control, networking and network communications. This Elecrow GSM/GPRS/EDGE SIM5360E 3G Shield seems to be the "latest and the greatest" as far as 3G and GPS, as far as I can see so far, but I has it drawbacks for sure.... (6 Replies)
Today I received my NB-IoT Arduino Shield for AIS (Thailand). Here is a "pinout" photo of the shield.
My shield looks just like the one above, for the most part. I'll post another photo of the actual device later.
When I received the shield in the mail, I went immediately to a local... (8 Replies)
Normally I have very good experiences buying from AliExpress, but in this case with Elecrow, I'm disappointed.
After confirming with Elecrow on AliExpress that their Elecrow GSM/GPRS/EDGE SIM5360E 3G Shield for Arduino would work with 3G SIM cards in Thailand, I purchased one. My plan was to... (1 Reply)
Here is a sketch to do basic testing for the Arduino UNO and the MLT-BT04.
This BLE module works with IOS (iPhone) and I'll add some details on my IOS testing with an iPhone in a follow-up post.
For now, here is the basic BLE (HM-10) sketch for the Arduino UNO:
/*
Arduino test-code... (7 Replies)
With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here:
ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages
The result turned out nice, I think. I like the look and... (10 Replies)
Normally I'm not into kits, but I thought my wife would enjoy this one since she is a big fan of robots and droids on StarWars!
We are done with the basic mechanical assembly and starting on the electronics assembly today.
The robot's "brain" consists of three levels. The Arduino board, on... (5 Replies)
Discussion started by: Neo
5 Replies
LEARN ABOUT DEBIAN
jifty::plugin
Jifty::Plugin(3pm) User Contributed Perl Documentation Jifty::Plugin(3pm)NAME
Jifty::Plugin - Describes a plugin to the Jifty framework
DESCRIPTION
Plugins are like mini-apps. They come in packages with share directories which provide static and template files; they provide actions;
they have dispatcher rules. To create the skeleton of a new plugin, you can use the command:
jifty plugin --name SomePlugin
To use a plugin in your Jifty application, find the "Plugins:" line in the "config.yml" file:
Plugins:
- SpiffyThing: {}
- SomePlugin:
arguments: to
the: constructor
The dispatcher for a plugin should live in "Jifty::Plugin::name::Dispatcher"; it is written like any other Jifty::Dispatcher. Plugin
dispatcher rules are checked before the application's rules; however, see "Plugins and rule ordering" in Jifty::Dispatcher for how to
manually specify exceptions to this.
Actions and models under a plugin's namespace are automatically discovered and made available to applications.
new
Sets up a new instance of this plugin. This is called by Jifty after reading the configuration file, and is supplied whatever plugin-
specific settings were in the config file. Note that because plugins affect Mason's component roots, adding plugins during runtime is not
supported.
init [ARGS]
Called by "new", this does any custom configuration that the plugin might need. It is passed the same parameters as "new", gleaned from
the configuration file.
new_request
Called right before every request. By default, does nothing.
template_root
Returns the root of the "HTML::Mason" template directory for this plugin
po_root
Returns the plugin's message catalog directory. Returns undef if it doesn't exist.
template_class
Returns the Template::Declare view package for this plugin
static_root
Returns the root of the static directory for this plugin
dispatcher
Returns the classname of the dispatcher class for this plugin
prereq_plugins
Returns an array of plugin module names that this plugin depends on.
version
Returns the database version of the plugin. Needs to be bumped any time the database schema needs to be updated. Plugins that do not
directly define any models don't need to worry about this.
bootstrapper
Returns the name of the class that can be used to bootstrap the database models. This normally returns the plugin's class name with
"::Bootstrap" added to the end. Plugin bootstrappers can be built in exactly the same way as application bootstraps.
See Jifty::Bootstrap.
upgrade_class
Returns the name of the class that can be used to upgrade the database models and schema (such as adding new data, fixing default values,
and renaming columns). This normally returns the plugin's class name with "::Upgrade" added to the end. Plugin upgrade classes can be built
in exactly the same was as application upgrade classes.
See Jifty::Upgrade.
table_prefix
Returns a prefix that will be placed in the front of all table names for plugin models. Be default, the plugin name is converted to an
identifier based upon the class name.
wrap
Takes a PSGI-$app closure and returns the wrapped one if your plugin wants to do something to the request handling process. See also
Plack::Middleware.
psgi_app_static
Returns a PSGI-$app that serves the static content of the plugin if any. The default is a <Plack::App::File> app with root set to plugin's
"static_root"
perl v5.14.2 2010-12-08 Jifty::Plugin(3pm)