See the original posting on DZone Python
For the Angular 5 client-side, check out the below repository:
For the Angular 5 client-side, check out the below repository:
This is not another praise piece for npm package management with Yarn, but rather a concise recipe for working with locally developed packages.
npm modules begin their lives when you
init them on your local dev machine, but there comes a point when you want to test them out or simply use them with other Node.js projects you have.
Last month, I published the "Considering Offshoring? Consider These Lessons Learned" article, which provided five lessons that I have learned when attempting to employ offshore or nearshore services to assist with development efforts. One of those learned lessons reminded us that:
"Service providers exist to provide services for their clientele. At the core, they are doing it as a means to generate revenue."
As a reader of this article, one might pose the question…
Another ForwardJS came and went in San Francisco and, as usual, I had a blast while I was there. This time around, I was representing Qlik with a sponsored workshop, so it was my first crack at getting Qlik Core into the hands of fresh-faced developers new to the engine? ?and here’s some things I learned.
If you have a middleware that needs to work on a specific path, you should implement it by mapping it to a route in ASP.NET Core 3.0, instead of just checking the path names. This post doesn’t handle regular middlewares, which need to work all request, or all requests inside a
At the Global MVP Summit 2019 in Redmond I attended the hackathon where I worked on my GraphQL middlewares for ASP.NET Core. I asked Glen Condron for a review of the API and the way the middleware gets configured. He told me that we did it all right. We followed the proposed way to provide and configure an ASP.NET Core middleware. But he also told me that there is a new way in ASP.NET Core 3.0 to use this kind of middleware.
In this article, we will tell you how it is done and how abandoning native apps might actually help a project.
I have an application that uses ASP.NET Core Identity with classic logins and there’s a need to cover this application with integration tests. Some tests are for anonymous users and others for authenticated users. This blog post shows how to set selectively set authenticated ASP.NET Core user identities for ASP.NET Core integration tests.
We start with an ASP.NET Core web application where basic authentication is done using ASP.NET Core Identity. There’s an integration tests project that uses a fake startup class and custom appsettings.json from my blog post, Using custom startup class with ASP.NET Core integration tests. Take a look at this post as there are some additional classes defined.
I’ve been building apps with queues lately and mostly using beanstalkd as my queue because it is very simple, very fast, and, on my platform, it is
[apt install beanstalkd] easy to install. I have also been using a handy web interface for beanstalkd which I like so much that I felt I ought to share! It’s beanstalk-console, which is a PHP-based web interface to one (or many) beanstalkd servers.
Beanstalkd is a very simple queueing system and I’ve enjoyed using it from a few different tech stacks. It uses "tubes" rather than channels, supports priorities, and uses a simple string for the body of the "job" on the queue.
I was doing some thinking recently. I was thinking about how I could make maps more useful than just displaying visual content on the screen when requested. While displaying map information on a screen is useful in many circumstances, it doesn’t make for the most exciting of examples. This lead me to thinking about things from a more interactive level.
Take the example of first responders, such as law enforcement, fire, and medical. It might not make the most sense for them to be looking and refreshing a map to find incidents. Instead, what if the map automatically refreshed and was synchronized between the first responders? What I mean by this is, what if incidents automatically appeared on everyone’s map at the same time without interaction?
My previous post demonstrated how to use a custom appsettings.js file with integration tests in ASP.NET Core. But in practice it’s not enough and very often we need a custom startup class that extends the one in the web application project to configure the application for integration tests. This blog post shows how to do this.
Using a custom startup class is a little bit tricky. I start again with a simple, classic integration test from the ASP.NET Core integration testing documentation.
This is the third part of our series on using Backendless with a React.js frontend app. You can catch up on the previous articles here: Part 1 and Part 2. If you’d like to jump in now, you can simply create a new Backendless app, clone our previous progress from our repository, and use this commit as an entry point for today’s article.
Our goal for today is to showcase integration with our Real-Time (we call it RT) database for delivering changes in your data table from the server to the client. We have previously written about implementation of RT in an Angular app ( "How to Use the Backendless Real-Time Database in Your Angular App"). If you’re interested in Angular or you just want to see difference between the usage of RT with React and Angular, we’d recommend you give that article a read.
In this post, I’ll show you how to receive webhooks in real time from GitHub.com, even if your CloudBees Core stuff is behind a firewall. You can generalize this to other services too such as BitBucket or DockerHub, or anything really that emits webhooks, but the instructions will be for GitHub projects hosted on github.com. The benefit, of course, is that you can use these public hosted services if you like, but your Core instances do not necessarily have to be directly open to the internet.
Just a very quick refresher on what webhooks are: Messages (often JSON, but not always) typically posted by HTTP(S) from a server to a client that is listening for events.
HTTP-RPC is an open-source framework for implementing RESTful and REST-like web services in Java. It is extremely lightweight and requires only a Java runtime environment and a servlet container. The entire framework is distributed as a single JAR file that is about 50KB in size, making it an ideal choice for applications where a minimal footprint is desired.
WebService type provides an abstract base class for REST-based web services. It extends the similarly abstract
HttpServlet class provided by the servlet API.
ASP.NET Core introduced the concept of TestServer for the integration testing of web applications. Integration tests need web applications to run with all the bells and whistles to make sure that all the components work together with no flaws. Often we need special settings for integration tests as web applications cannot use live services and the easiest way to do it is to use a special appsettings.json file. This blog post shows how to do it.
Let’s start with minimalistic integration test from ASP.NET Core integration tests document.
In the previous article in this series, we started working on a single-page application which is based on a combination of and with Backendless for the backend. If you missed that article, we recommend you to start there. If you already have a Backendless account and you are already familiar with a React/Redux stack, you can just clone our previous progress from this commit, create a new Backendless app, and use it as an entry point for today’s article. Let me describe the main goal for this article and what we plan to cover:
PersonsEditorfor creating and updating persons.
As you can imagine, our app will grow up quite a bit during this article, so we need to move logic for rendering our list of persons to a separate class/component. There we will keep a data connection and UI representation, and it will also help us in the future to manage Real-Time subscriptions.
In the video below, we take a closer look at how to configure the welcome file list in web.xml in servlets?. Let’s get started!
SyntaxError: "x" is a reserved identifier (Firefox) SyntaxError: Unexpected reserved word (Chrome)
Above is the error messages you will receive if you use such words by accident. Seasoned JS developers, too, commit such blunders while coding.
Frequently, when disassembling apps or applications I need to determine weather the app is implemented in Objective-C or Swift. You can do that in a variety of ways, usually, including looking into the application via otool or jtool to understand what libraries the app needs or looking for tags in various function names (like there word "swift," for example).
I thought it would be interesting to start to compare the function semantics in Objective-C and Swift to see how they differ. I’ve recently gone over function vs. message passing semantics to prepare for this comparison, so we can start to take a look at Swift code, which is much more complex than Objective-C. We’re going use two similar programs for this comparison – though that similarity is only skin deep, as we’ll see.
In this article, we will start by creating a new Backendless App and building a simple React app. Our demo app will be an Address Book app, so to get started we will show how to load and display some data from the server. In the future, we will modernize the application by adding more functionality.
ONLYOFFICE is a free and open source web-based office suite that can be easily deployed on your own server, integrated with your web application, and extended with your own plugins.
A plugin is the simplest way to add missing or additional features, like Symbol Table. Using plugins you can easily integrate document editors with any other editor, for example, to edit images. or connect any third-party service, be it online, like YouTube, or self-hosted, like Highlight Code.