Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114774
interpreted = N
texte = 2400 --Apple-Mail=_86DCEA5A-4EE0-4E35-B6A2-3154EC8128DD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > I know this is about hosting, but the biggest reason I struggle with = products like Toolset.com (which has a cumbersome = interface that kinda does what WebDNA can but which sucks because = they=E2=80=99re trying to do it with PHP), is because it makes no sense = to build a website with an admin backend from scratch. The primary = components of every website should be pre-built packaged stuff that gets = the CSS treatment. That gets the entire site - with a back end - up and = running in a few minutes. Everyone should have a look at the new eCommerce module that Christophe = has available Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 20 Sep 2019, at 02:13, Patrick McCormick = wrote: >=20 > I=E2=80=99ve been using futurehosting.com = after doing a ton of searching. Prices are reasonable but the primary = advantage is a ticketed support system with under 5 minute response by = qualified people. >=20 > I run a large pile of WordPress websites and other things. The = ecosystem for software used by most hosting providers is really = modularized and reliable. They use things like Softaculo for bundling = software packages and then there are intuitive interfaces for = installation and management. No reason that WebDNA isn=E2=80=99t = already packaged as such. It should already have a free version = available among the rest of the internet world. >=20 > Also - once bundles that way, it becomes immediately available for = lots of additional situations. Docker.com comes to = mind. Imagine only having to send a single link to a config file and = anyone can be running a duplicate instance of whatever complicated = arrangement you might have built onto a complicated server. >=20 > The rest of the web world has moved way beyond WebDNA, but WebDNA does = something so much better than anything else, I believe it=E2=80=99s just = a matter of packaging WebDNA to make it a tremendous success. The = entire WebDNA language could operate seamlessly within a WordPress = installation. Yes - you do need to understand WordPress, but if I can = set up a WordPress site quickly with a pre-built theme, then use a = WebDNA plugin version to build the custom parts of the site & even = interact with the WordPress database dynamically, that is exactly what = the future will eventually look like. >=20 > I know this is about hosting, but the biggest reason I struggle with = products like Toolset.com (which has a cumbersome = interface that kinda does what WebDNA can but which sucks because = they=E2=80=99re trying to do it with PHP), is because it makes no sense = to build a website with an admin backend from scratch. The primary = components of every website should be pre-built packaged stuff that gets = the CSS treatment. That gets the entire site - with a back end - up and = running in a few minutes. >=20 > Than, once particular functions unique to that business and its site = are defined, build those in WebDNA. IT would have a staggering effect = on the entire internet if there were any other web language than PHP. = PHP is a giant drag on the advancement of humanity. It also need an = entirely separate database system which comes with its own separate = programming language. WordPress got big because there was simply no = other reasonable way to build websites in one=E2=80=99s own lifetime = without it. >=20 > But, since that infrastructure is already fast & reliable, why = reinvent the wheel? The only time you need to step out of the basic = construct of what a thing like WordPress provides is when you need to = create some non-standard function on a website for a particular business = situation. If the website needs to display & track pizza deliveries, = enter WebDNA. In the back end of WordPress, WebDNA would provide an = interface for creating the stuff needed & that interface would provide = hooks into the WordPress data so how and where WebDNA data lived could = be handled on the fly. =20 >=20 > This world would mean that I could grab hosting from a fully managed = provider, or just fire a docker image onto a google instance and be up = and running with WordPress. Next, I would install the WebDNA plugin and = connect the licensing to the WebDNA server and build the custom stuff. >=20 > I would never again worry about a physical server. Everything = currently on the cloud is capable of running WebDNA, provided the WebDNA = guys get someone who knows how to bundle and package it so it plays = correctly with the existing infrastructure of this stuff. >=20 > The entire billing system I use for customers is on the same cloud = based server I use. Monthly revenue automatically flows into a PayPal = account. I don=E2=80=99t have to produce a single invoice for hosting = ever and if anyone=E2=80=99s credit card fails, they get auto notified = what day their site will go down unless its rectified. All support = tickets flow directly to the 24x7 staff because its a fully managed = server. >=20 > C=E2=80=99mom WebDNA guys, the water=E2=80=99s fine in this here pool! = Jump in!! >=20 >=20 >=20 >> On Sep 19, 2019, at 10:50 AM, Brian Harrington = > wrote: >>=20 >> LOL u really in deep when the webdna guys don't know what ya (you = lol) saying... LOL (Laughing Out Loud) >>=20 >> On Thu, Sep 19, 2019 at 3:27 AM Scott @ Itsula > wrote: >> Yh. Yes. Slang really, apologies. >>=20 >> =20 >> IaaS. >>=20 >> Infrastructure as a Service. >>=20 >> Renting servers up to and including a managed and patched OS = (operating system, Ubuntu for example). >>=20 >> =20 >> PaaS. >>=20 >> Platform as a Service. >>=20 >> Renting servers up to and including a managed application on top of a = managed OS. >>=20 >> The application in this example would be a WebDNA instance. >>=20 >> =20 >> PoPs. Points of presence. Locations where the IaaS or PaaS are served = from, for example London, Sydney. >>=20 >> =20 >> Microsoft Azure, IBM SoftLayer, Amazon Web Services are all examples = of the larger IaaS/PaaS providers. >>=20 >> =20 >> VPS are spins on either a shared or dedicated server. IaaS /PaaS = brings all of the other toys to the party. >>=20 >> =20 >> One other common global layer is SaaS, Software as a service. This is = where typically a web-enabled application is served with a = subscription-based revenue model. >>=20 >> =20 >> Hope you're ok Ken. We've not met, but you don't seem all that happy = in your written tone to date. Chin up, chap, we=E2=80=99re all on the = same (non ASP/PHP) side here surely! >>=20 >> =20 >> Regards, >>=20 >> Scott >>=20 >> =20 >> =20 >> =20 >> From: WebDNA Solutions >> Sent: 18 September 2019 20:30 >> Cc: talk@webdna.us >> Subject: Re: [WebDNA] Sorry WebDNA server not running /Template = ERROR/ Slow speeds >>=20 >> =20 >> > Yh, I have to agree with the use of IaaS. >> >=20 >> > I would be happy to put together a talklist agreed WebDNA >> > PaaS with global PoPs if that's of interest to many? >>=20 >> Yh? >> IaaS? >> PaaS? >> PoPs? >>=20 >> Right. >>=20 >> I have no idea what the h*** you're talking about. >>=20 >> Maybe that's a good thing. Who knows?=20 >>=20 >> Regards, >> Kenneth Grome >> WebDNA Solutions >> http://www.webdnasolutions.com >> Urgent/Emergency Phone: (228) 222-2917 >> Website, Database, Network, and Communication Systems >>=20 >>=20 >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list talk@webdna.us >> To unsubscribe, E-mail to: talk-leave@webdna.us = >> archives: http://www.webdna.us/page.dna?numero=3D55 = >> Bug Reporting: support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >>=20 >> --=20 >> Brian Harrington >> Auto Glass Xpress >> 2655 Millersport Hwy. Suite 1063 >> Getzville, NY 14068 >> (716) 861-2029 >> www.Auto-Glass-Xpress.com = ---------------------------------------= ------------------ This message is sent to you because you are = subscribed to the mailing list talk@webdna.us To = unsubscribe, E-mail to: talk-leave@webdna.us = archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us --Apple-Mail=_86DCEA5A-4EE0-4E35-B6A2-3154EC8128DD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
I know this is about hosting, but = the biggest reason I struggle with products like Toolset.com (which has = a cumbersome interface that kinda does what WebDNA can but which sucks = because they=E2=80=99re trying to do it with PHP), is because it makes = no sense to build a website with an admin backend from scratch. =  The primary components of every website should be pre-built = packaged stuff that gets the CSS treatment.  That gets the entire = site - with a back end - up and running in a few = minutes.

Everyone = should have a look at the new eCommerce module that Christophe has = available

Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







On 20 Sep 2019, at 02:13, Patrick McCormick <duganmccormick@gmail.com> wrote:

I=E2=80=99ve been = using futurehosting.com after doing a ton of searching. =  Prices are reasonable but the primary advantage is a ticketed = support system with under 5 minute response by qualified people.

I run a large pile of = WordPress websites and other things.  The ecosystem for software = used by most hosting providers is really modularized and reliable. =  They use things like Softaculo for bundling software packages and = then there are intuitive interfaces for installation and management. =  No reason that WebDNA isn=E2=80=99t already packaged as such. =  It should already have a free version available among the rest of = the internet world.

Also - once bundles that way, it becomes immediately = available for lots of additional situations.  Docker.com comes to = mind.  Imagine only having to send a single link to a config file = and anyone can be running a duplicate instance of whatever complicated = arrangement you might have built onto a complicated server.

The rest of the web = world has moved way beyond WebDNA, but WebDNA does something so much = better than anything else, I believe it=E2=80=99s just a matter of = packaging WebDNA to make it a tremendous success.  The entire = WebDNA language could operate seamlessly within a WordPress = installation.  Yes - you do need to understand WordPress, but if I = can set up a WordPress site quickly with a pre-built theme, then use a = WebDNA plugin version to build the custom parts of the site & even = interact with the WordPress database dynamically, that is exactly what = the future will eventually look like.

I know this is about hosting, but the = biggest reason I struggle with products like Toolset.com (which has = a cumbersome interface that kinda does what WebDNA can but which sucks = because they=E2=80=99re trying to do it with PHP), is because it makes = no sense to build a website with an admin backend from scratch. =  The primary components of every website should be pre-built = packaged stuff that gets the CSS treatment.  That gets the entire = site - with a back end - up and running in a few minutes.

Than, once particular = functions unique to that business and its site are defined, build those = in WebDNA.  IT would have a staggering effect on the entire = internet if there were any other web language than PHP.  PHP is a = giant drag on the advancement of humanity.  It also need an = entirely separate database system which comes with its own separate = programming language.  WordPress got big because there was simply = no other reasonable way to build websites in one=E2=80=99s own lifetime = without it.

But,= since that infrastructure is already fast & reliable, why reinvent = the wheel?  The only time you need to step out of the basic = construct of what a thing like WordPress provides is when you need to = create some non-standard function on a website for a particular business = situation.  If the website needs to display & track pizza = deliveries, enter WebDNA.  In the back end of WordPress, WebDNA = would provide an interface for creating the stuff needed & that = interface would provide hooks into the WordPress data so how and where = WebDNA data lived could be handled on the fly.  

This world would mean = that I could grab hosting from a fully managed provider, or just fire a = docker image onto a google instance and be up and running with = WordPress.  Next, I would install the WebDNA plugin and connect the = licensing to the WebDNA server and build the custom stuff.

I would never again = worry about a physical server.  Everything currently on the cloud = is capable of running WebDNA, provided the WebDNA guys get someone who = knows how to bundle and package it so it plays correctly with the = existing infrastructure of this stuff.

The entire billing system I use for = customers is on the same cloud based server I use.  Monthly revenue = automatically flows into a PayPal account.  I don=E2=80=99t have to = produce a single invoice for hosting ever and if anyone=E2=80=99s credit = card fails, they get auto notified what day their site will go down = unless its rectified.  All support tickets flow directly to the = 24x7 staff because its a fully managed server.

C=E2=80=99mom WebDNA guys, the = water=E2=80=99s fine in this here pool!  Jump in!!



On Sep 19, 2019, at 10:50 AM, Brian Harrington <autoglasswny@gmail.com> wrote:

LOL u really in deep when the webdna guys don't know what ya = (you lol) saying... LOL (Laughing Out Loud)

On Thu, Sep = 19, 2019 at 3:27 AM Scott @ Itsula <scott@itsula.co.uk> = wrote:

Yh. Yes. Slang really, apologies.

 

IaaS.

Infrastructure as a = Service.

Renting = servers up to and including a managed and patched OS (operating system, = Ubuntu for example).

 

PaaS.

Platform as a Service. =

Renting servers = up to and including a managed application on top of a managed OS.

The application in = this example would be a WebDNA instance.

 

PoPs. Points of = presence. Locations where the IaaS or PaaS are served from, for example = London, Sydney.

 

Microsoft Azure, IBM = SoftLayer, Amazon Web Services are all examples of the larger IaaS/PaaS = providers.

 

VPS are spins on = either a shared or dedicated server. IaaS /PaaS brings all of the other = toys to the party.

 

One other common = global layer is SaaS, Software as a service. This is where typically a = web-enabled application is served with a subscription-based revenue = model.

 

Hope you're ok Ken. = We've not met, but you don't seem all that happy in your written tone to = date. Chin up, chap, we=E2=80=99re all on the same (non ASP/PHP) side = here surely!

 

Regards,

Scott

 
 
 

From: WebDNA Solutions
Sent: 18 September 2019 20:30
Cc: talk@webdna.us
Subject: Re: [WebDNA] Sorry WebDNA server not running = /Template ERROR/ Slow speeds

 
> Yh, I have to = agree with the use of IaaS.
>
> I would be happy to put together a talklist agreed WebDNA
> PaaS with global PoPs if that's of interest to many?

Yh?
IaaS?
PaaS?
PoPs?

Right.

I have no idea what the h*** you're talking about.

Maybe that's a good thing. Who knows?

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Urgent/Emergency Phone: (228) 222-2917
Website, Database, Network, and Communication Systems



---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55= Bug Reporting: support@webdna.us


--
Brian = Harrington
Auto Glass Xpress
2655 Millersport Hwy. Suite 1063
Getzville, NY 14068
(716) = 861-2029
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_86DCEA5A-4EE0-4E35-B6A2-3154EC8128DD-- . Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds ("Terry Nair" 2019)
  2. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (Stuart Tremain 2019)
  3. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Tom Duke 2019)
  4. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow ("Scott @ Itsula" 2019)
  5. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (christophe.billiottet@webdna.us 2019)
  6. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow ("Scott @ Itsula" 2019)
  7. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (WebDNA Solutions 2019)
  8. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow ("Scott @ Itsula" 2019)
  9. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow ("Scott @ Itsula" 2019)
  10. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (WebDNA Solutions 2019)
  11. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (WebDNA Solutions 2019)
  12. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (Patrick McCormick 2019)
  13. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Brian Harrington 2019)
  14. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow ("Scott @ Itsula" 2019)
  15. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Brian Harrington 2019)
  16. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Stuart Tremain 2019)
  17. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Brian Harrington 2019)
  18. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (WebDNA Solutions 2019)
  19. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (WebDNA Solutions 2019)
  20. RE: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow ("Scott @ Itsula" 2019)
  21. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Brian Harrington 2019)
  22. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (WebDNA Solutions 2019)
  23. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (Stuart Tremain 2019)
  24. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Brian Harrington 2019)
  25. Re: [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow (H - Powerpalle 2019)
  26. [WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (Brian Harrington 2019)
2400 --Apple-Mail=_86DCEA5A-4EE0-4E35-B6A2-3154EC8128DD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > I know this is about hosting, but the biggest reason I struggle with = products like Toolset.com (which has a cumbersome = interface that kinda does what WebDNA can but which sucks because = they=E2=80=99re trying to do it with PHP), is because it makes no sense = to build a website with an admin backend from scratch. The primary = components of every website should be pre-built packaged stuff that gets = the CSS treatment. That gets the entire site - with a back end - up and = running in a few minutes. Everyone should have a look at the new eCommerce module that Christophe = has available Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 20 Sep 2019, at 02:13, Patrick McCormick = wrote: >=20 > I=E2=80=99ve been using futurehosting.com = after doing a ton of searching. Prices are reasonable but the primary = advantage is a ticketed support system with under 5 minute response by = qualified people. >=20 > I run a large pile of WordPress websites and other things. The = ecosystem for software used by most hosting providers is really = modularized and reliable. They use things like Softaculo for bundling = software packages and then there are intuitive interfaces for = installation and management. No reason that WebDNA isn=E2=80=99t = already packaged as such. It should already have a free version = available among the rest of the internet world. >=20 > Also - once bundles that way, it becomes immediately available for = lots of additional situations. Docker.com comes to = mind. Imagine only having to send a single link to a config file and = anyone can be running a duplicate instance of whatever complicated = arrangement you might have built onto a complicated server. >=20 > The rest of the web world has moved way beyond WebDNA, but WebDNA does = something so much better than anything else, I believe it=E2=80=99s just = a matter of packaging WebDNA to make it a tremendous success. The = entire WebDNA language could operate seamlessly within a WordPress = installation. Yes - you do need to understand WordPress, but if I can = set up a WordPress site quickly with a pre-built theme, then use a = WebDNA plugin version to build the custom parts of the site & even = interact with the WordPress database dynamically, that is exactly what = the future will eventually look like. >=20 > I know this is about hosting, but the biggest reason I struggle with = products like Toolset.com (which has a cumbersome = interface that kinda does what WebDNA can but which sucks because = they=E2=80=99re trying to do it with PHP), is because it makes no sense = to build a website with an admin backend from scratch. The primary = components of every website should be pre-built packaged stuff that gets = the CSS treatment. That gets the entire site - with a back end - up and = running in a few minutes. >=20 > Than, once particular functions unique to that business and its site = are defined, build those in WebDNA. IT would have a staggering effect = on the entire internet if there were any other web language than PHP. = PHP is a giant drag on the advancement of humanity. It also need an = entirely separate database system which comes with its own separate = programming language. WordPress got big because there was simply no = other reasonable way to build websites in one=E2=80=99s own lifetime = without it. >=20 > But, since that infrastructure is already fast & reliable, why = reinvent the wheel? The only time you need to step out of the basic = construct of what a thing like WordPress provides is when you need to = create some non-standard function on a website for a particular business = situation. If the website needs to display & track pizza deliveries, = enter WebDNA. In the back end of WordPress, WebDNA would provide an = interface for creating the stuff needed & that interface would provide = hooks into the WordPress data so how and where WebDNA data lived could = be handled on the fly. =20 >=20 > This world would mean that I could grab hosting from a fully managed = provider, or just fire a docker image onto a google instance and be up = and running with WordPress. Next, I would install the WebDNA plugin and = connect the licensing to the WebDNA server and build the custom stuff. >=20 > I would never again worry about a physical server. Everything = currently on the cloud is capable of running WebDNA, provided the WebDNA = guys get someone who knows how to bundle and package it so it plays = correctly with the existing infrastructure of this stuff. >=20 > The entire billing system I use for customers is on the same cloud = based server I use. Monthly revenue automatically flows into a PayPal = account. I don=E2=80=99t have to produce a single invoice for hosting = ever and if anyone=E2=80=99s credit card fails, they get auto notified = what day their site will go down unless its rectified. All support = tickets flow directly to the 24x7 staff because its a fully managed = server. >=20 > C=E2=80=99mom WebDNA guys, the water=E2=80=99s fine in this here pool! = Jump in!! >=20 >=20 >=20 >> On Sep 19, 2019, at 10:50 AM, Brian Harrington = > wrote: >>=20 >> LOL u really in deep when the webdna guys don't know what ya (you = lol) saying... LOL (Laughing Out Loud) >>=20 >> On Thu, Sep 19, 2019 at 3:27 AM Scott @ Itsula > wrote: >> Yh. Yes. Slang really, apologies. >>=20 >> =20 >> IaaS. >>=20 >> Infrastructure as a Service. >>=20 >> Renting servers up to and including a managed and patched OS = (operating system, Ubuntu for example). >>=20 >> =20 >> PaaS. >>=20 >> Platform as a Service. >>=20 >> Renting servers up to and including a managed application on top of a = managed OS. >>=20 >> The application in this example would be a WebDNA instance. >>=20 >> =20 >> PoPs. Points of presence. Locations where the IaaS or PaaS are served = from, for example London, Sydney. >>=20 >> =20 >> Microsoft Azure, IBM SoftLayer, Amazon Web Services are all examples = of the larger IaaS/PaaS providers. >>=20 >> =20 >> VPS are spins on either a shared or dedicated server. IaaS /PaaS = brings all of the other toys to the party. >>=20 >> =20 >> One other common global layer is SaaS, Software as a service. This is = where typically a web-enabled application is served with a = subscription-based revenue model. >>=20 >> =20 >> Hope you're ok Ken. We've not met, but you don't seem all that happy = in your written tone to date. Chin up, chap, we=E2=80=99re all on the = same (non ASP/PHP) side here surely! >>=20 >> =20 >> Regards, >>=20 >> Scott >>=20 >> =20 >> =20 >> =20 >> From: WebDNA Solutions >> Sent: 18 September 2019 20:30 >> Cc: talk@webdna.us >> Subject: Re: [WebDNA] Sorry WebDNA server not running /Template = ERROR/ Slow speeds >>=20 >> =20 >> > Yh, I have to agree with the use of IaaS. >> >=20 >> > I would be happy to put together a talklist agreed WebDNA >> > PaaS with global PoPs if that's of interest to many? >>=20 >> Yh? >> IaaS? >> PaaS? >> PoPs? >>=20 >> Right. >>=20 >> I have no idea what the h*** you're talking about. >>=20 >> Maybe that's a good thing. Who knows?=20 >>=20 >> Regards, >> Kenneth Grome >> WebDNA Solutions >> http://www.webdnasolutions.com >> Urgent/Emergency Phone: (228) 222-2917 >> Website, Database, Network, and Communication Systems >>=20 >>=20 >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list talk@webdna.us >> To unsubscribe, E-mail to: talk-leave@webdna.us = >> archives: http://www.webdna.us/page.dna?numero=3D55 = >> Bug Reporting: support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: = talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us >>=20 >> --=20 >> Brian Harrington >> Auto Glass Xpress >> 2655 Millersport Hwy. Suite 1063 >> Getzville, NY 14068 >> (716) 861-2029 >> www.Auto-Glass-Xpress.com = ---------------------------------------= ------------------ This message is sent to you because you are = subscribed to the mailing list talk@webdna.us To = unsubscribe, E-mail to: talk-leave@webdna.us = archives: = http://www.webdna.us/page.dna?numero=3D55 = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list = talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: = http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us --Apple-Mail=_86DCEA5A-4EE0-4E35-B6A2-3154EC8128DD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
I know this is about hosting, but = the biggest reason I struggle with products like Toolset.com (which has = a cumbersome interface that kinda does what WebDNA can but which sucks = because they=E2=80=99re trying to do it with PHP), is because it makes = no sense to build a website with an admin backend from scratch. =  The primary components of every website should be pre-built = packaged stuff that gets the CSS treatment.  That gets the entire = site - with a back end - up and running in a few = minutes.

Everyone = should have a look at the new eCommerce module that Christophe has = available

Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







On 20 Sep 2019, at 02:13, Patrick McCormick <duganmccormick@gmail.com> wrote:

I=E2=80=99ve been = using futurehosting.com after doing a ton of searching. =  Prices are reasonable but the primary advantage is a ticketed = support system with under 5 minute response by qualified people.

I run a large pile of = WordPress websites and other things.  The ecosystem for software = used by most hosting providers is really modularized and reliable. =  They use things like Softaculo for bundling software packages and = then there are intuitive interfaces for installation and management. =  No reason that WebDNA isn=E2=80=99t already packaged as such. =  It should already have a free version available among the rest of = the internet world.

Also - once bundles that way, it becomes immediately = available for lots of additional situations.  Docker.com comes to = mind.  Imagine only having to send a single link to a config file = and anyone can be running a duplicate instance of whatever complicated = arrangement you might have built onto a complicated server.

The rest of the web = world has moved way beyond WebDNA, but WebDNA does something so much = better than anything else, I believe it=E2=80=99s just a matter of = packaging WebDNA to make it a tremendous success.  The entire = WebDNA language could operate seamlessly within a WordPress = installation.  Yes - you do need to understand WordPress, but if I = can set up a WordPress site quickly with a pre-built theme, then use a = WebDNA plugin version to build the custom parts of the site & even = interact with the WordPress database dynamically, that is exactly what = the future will eventually look like.

I know this is about hosting, but the = biggest reason I struggle with products like Toolset.com (which has = a cumbersome interface that kinda does what WebDNA can but which sucks = because they=E2=80=99re trying to do it with PHP), is because it makes = no sense to build a website with an admin backend from scratch. =  The primary components of every website should be pre-built = packaged stuff that gets the CSS treatment.  That gets the entire = site - with a back end - up and running in a few minutes.

Than, once particular = functions unique to that business and its site are defined, build those = in WebDNA.  IT would have a staggering effect on the entire = internet if there were any other web language than PHP.  PHP is a = giant drag on the advancement of humanity.  It also need an = entirely separate database system which comes with its own separate = programming language.  WordPress got big because there was simply = no other reasonable way to build websites in one=E2=80=99s own lifetime = without it.

But,= since that infrastructure is already fast & reliable, why reinvent = the wheel?  The only time you need to step out of the basic = construct of what a thing like WordPress provides is when you need to = create some non-standard function on a website for a particular business = situation.  If the website needs to display & track pizza = deliveries, enter WebDNA.  In the back end of WordPress, WebDNA = would provide an interface for creating the stuff needed & that = interface would provide hooks into the WordPress data so how and where = WebDNA data lived could be handled on the fly.  

This world would mean = that I could grab hosting from a fully managed provider, or just fire a = docker image onto a google instance and be up and running with = WordPress.  Next, I would install the WebDNA plugin and connect the = licensing to the WebDNA server and build the custom stuff.

I would never again = worry about a physical server.  Everything currently on the cloud = is capable of running WebDNA, provided the WebDNA guys get someone who = knows how to bundle and package it so it plays correctly with the = existing infrastructure of this stuff.

The entire billing system I use for = customers is on the same cloud based server I use.  Monthly revenue = automatically flows into a PayPal account.  I don=E2=80=99t have to = produce a single invoice for hosting ever and if anyone=E2=80=99s credit = card fails, they get auto notified what day their site will go down = unless its rectified.  All support tickets flow directly to the = 24x7 staff because its a fully managed server.

C=E2=80=99mom WebDNA guys, the = water=E2=80=99s fine in this here pool!  Jump in!!



On Sep 19, 2019, at 10:50 AM, Brian Harrington <autoglasswny@gmail.com> wrote:

LOL u really in deep when the webdna guys don't know what ya = (you lol) saying... LOL (Laughing Out Loud)

On Thu, Sep = 19, 2019 at 3:27 AM Scott @ Itsula <scott@itsula.co.uk> = wrote:

Yh. Yes. Slang really, apologies.

 

IaaS.

Infrastructure as a = Service.

Renting = servers up to and including a managed and patched OS (operating system, = Ubuntu for example).

 

PaaS.

Platform as a Service. =

Renting servers = up to and including a managed application on top of a managed OS.

The application in = this example would be a WebDNA instance.

 

PoPs. Points of = presence. Locations where the IaaS or PaaS are served from, for example = London, Sydney.

 

Microsoft Azure, IBM = SoftLayer, Amazon Web Services are all examples of the larger IaaS/PaaS = providers.

 

VPS are spins on = either a shared or dedicated server. IaaS /PaaS brings all of the other = toys to the party.

 

One other common = global layer is SaaS, Software as a service. This is where typically a = web-enabled application is served with a subscription-based revenue = model.

 

Hope you're ok Ken. = We've not met, but you don't seem all that happy in your written tone to = date. Chin up, chap, we=E2=80=99re all on the same (non ASP/PHP) side = here surely!

 

Regards,

Scott

 
 
 

From: WebDNA Solutions
Sent: 18 September 2019 20:30
Cc: talk@webdna.us
Subject: Re: [WebDNA] Sorry WebDNA server not running = /Template ERROR/ Slow speeds

 
> Yh, I have to = agree with the use of IaaS.
>
> I would be happy to put together a talklist agreed WebDNA
> PaaS with global PoPs if that's of interest to many?

Yh?
IaaS?
PaaS?
PoPs?

Right.

I have no idea what the h*** you're talking about.

Maybe that's a good thing. Who knows?

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Urgent/Emergency Phone: (228) 222-2917
Website, Database, Network, and Communication Systems



---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, E-mail to: talk-leave@webdna.us
archives: http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55= Bug Reporting: support@webdna.us


--
Brian = Harrington
Auto Glass Xpress
2655 Millersport Hwy. Suite 1063
Getzville, NY 14068
(716) = 861-2029
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_86DCEA5A-4EE0-4E35-B6A2-3154EC8128DD-- . Stuart Tremain

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

OFF-TOPIC: WebDNA hosting ... (2003) Shipping charges (1998) another problem (1997) [WebDNA] [WSC] WebDNA Development Summit (2014) 2nd WebCatalog2 Feature Request (1996) OH CRAP!!!!!- Template not found error!!! (1999) Re:FYI: Error message (1996) Removing a character (2000) Please please help (2001) if/then/else in founditems (2001) Showif date range comparison (1999) WC2.0 Memory Requirements (1997) Caching [include] files ... (1997) [WebDNA] Which linux distros for webdna? (2008) Log-in Scheme (2003) Initiating NewCart (1997) emailer error 103 part ii (1997) suggestion (1997) [WebDNA] i wish we could require one *amongst of a collection* of search comparisons/params (2011) Redirect (2003)