Easy Tools
Banda Philpot
Without your help, this tool will not be made.
With the Kickstarter not meeting the goal, we will be moving forward with only funding from pre-orders here and a loan. Raising the funding will allow us to make the number of tools needed to meet demand in a strong lifelong material. We will be able to make hundreds if not thousands of the tools each day instead of just 10. They will be far stronger than the 3D prototypes you have seen or used thus far.
Order now to make this a reality. By placing a pre-order on this site, you will be adding your funds toward the creation of the tool. orders will be fulfilled in the order received so the first person who made a pre-order will be the first person to receive the tool.
Since the Kickstarter campaign did not reach the funding goal, nobody will be charged and the funding will not be received through that avenue. the only way to get on the list to receive the tool early is to place a pre-order through our shop page here.
I am pleasantly surprised with how well these pliers worked! I know these are a work in progress, but they have so much potential and I am excited to see where these pliers go in the future. These are officially added to my crochet tool kit.
100% confidence no hidden cybercriminals in your clients' M365 tenants PLUS a faster helpdesk system, consistent M365 security setup. Giving you happier customers, more Monthly Recurring Revenue AND you sleep better at night.
Fantastic suite of tools, which makes looking after 365 clients as simple as opening one product and having all the tools at your fingertips. solving 3rd line IT Support queries by the 1st Line workers This has allowed the senior engineers to focus on the project work
The amount of time it saves us is staggering when it comes to quickly accessing each of our clients. Additionally, the reports that notify us when a potential breach has happened makes it incredibly easy to stop the bad guys FAST. In the unfortunate circumstance where a user is phished, or uses too weak a password and a system is breached, you're racing against the clock to kick the bad guys out before substantial damage can be done. MSPET makes it easy to be alerted.
We are now far less likely to suffer a damaging breach due to near instant notification once a suspicious login happens. We are based within the UK, as are all of our clients and so whenever a login from abroad is detected, we are notified and can block the account rapidly. Similarly, if any suspicious external forwards or users are detected, we can remove them immediately.
Making Office 365 admin much easier to onboard clients new hires, offboard clients leavers. Great for monitoring multiple tenants for licensing, security issues and makes reporting easy. Enables techs to do everything in one place rather than navigating through multiple tenants on O365 partner admin.
It's very easy to navigate the various sections, and saves time with lots of otherwise slow tasks. The direct integration to manage all clients in a central place is very helpful. Saves us logging in countless times to various tenants. The reporting and alerting are excellent, and provide a great upsell to our clients with the reporting. Onboarding and offboarding is so handy now. Fantastic tool for any MSP.
The integrated Onboarding and Offboarding saves us a lot of time. Very quick access to all our tenants, and so increases our turn around time on tickets etc as we can rely on MSP Easy Tools to do the heavy lifting.
Monitoring, alerting, reporting, and scripting for Microsoft 365 best practices and cybersecurity. Monitoring and for external forwarding rules, templates for best practices, reporting on a variety of Microsoft 365 tenant settings, and awesome scripting tools that reduce the amount of time needed to accomplish tasks for your Service Desk.
The cybersecurity landscape continues to change, risks continue to increase, and Microsoft 365 cybersecurity best practices is a black hole for many customers and MSPs. MSP Easy Tools addresses these concerns. It also leads to an increase in your MRR, as it is an easy upsell for existing MSP clients.
We've been there, done that, and developed the tools, including the cyber security dashboard, to help you succeed. Our experience in the MSP world has led us to develop solutions that are used by MSPs around the world. Our community of MSPs helps us stay on top of emerging trends and needs, ensuring that we're always providing the best solutions, including MSP security tools, to help you achieve your goals.
Features of the social posting tool include scheduling content, reading and responding to conversations on Facebook, Instagram, or LinkedIn, resharing content, and EASILY sharing your email marketing campaigns to social media. You can even view your social post reporting to see how your posts are performing.
When I worked at a nonprofit many years ago, I tried to find as many free tools to manage our various social media accounts as possible. Two I used at the time were Hootsuite and Buffer. Both allowed me to schedule posts across various social media platforms, which helped with time management. One of the main drawbacks I had with both of these, however, was that they did not offer any analytics or reporting on their basic plans, you had to upgrade to access.
Ultimately, I had to use Google Analytics, Facebook, Instagram, and Twitter's native reporting to gauge success. It was time-intensive but with no budget it was what we had to work with.
Social media is a powerful tool for businesses to reach targeted audiences. We have outlined steps to developing and implementing a social media marketing campaign in this article: -step-involved-in-developing-and-implementing-a-social-m...
welcome to the forums. The Laminas API tools can be executed in development and in production mode. If the API Tools are in development mode, following modules are loaded additionally via development.config.php in your config folder.
Conversely, this means that the both modules mentioned are not loaded in production and therefore do not have to be present in the modules folder. I would always recommend building up a detailed REST API with the admin UI and deploy it without development settings. Basically this is a code only solution.
The API Tools map HTTP methods to the respective listener methods. If a method is not implemented, an APIProblemResponse will be returned. Normally you 'll see a HTTP 501 Not Implemented response in that case. Content negotiation / validation works only with POST, PUT and PATCH. You can add separate filters and validators for each HTTP method specifically.
Note: Content Validation Request Methods
Content Validation currently only works for POST, PATCH, and PUT requests. If you need to validate query string parameters, you will need to write your own logic for those tasks.
Not considering the Admin tools UI and the various dependencies for a moment, how the module configuration should be structured in order to instantiate a new RestController and make it available on a certain route?
1. Controllers
The Laminas API Tools are event driven. Sure, there is a basic rest controller. But this one just handles the different resources by different routes and HTTP methods. The Laminas\ApiTools\Rest\RestController extends the Laminas\Mvc\Controller\AbstractRestfulController. In normal use cases you don 't need another controller for REST API Services, because this controller calls your specific resource.
2. Resources
A resource is an event listener that will be triggered by the rest controller. A resource contains all the methods you need when acting as a rest service: create, delete, deleteList, fetch, fetchAll, patch, patchList, replaceList and update. If you don 't implement any of this methods in your resource, the response is 405.
Your setup is quite easy and creates a simple REST controller that will work. But this implementation does not use a single advantage of the API tools. No validation, no content matching, no automatic handling of request and return headers. You literally do everything by hand here. There is absolutely no need for that.
From now on you can programmatically define your resources and api endpoints. Even some basic authentication listeners are implemented in the base config of laminas-api-tools/api-tools. The following steps describe, how to define an endpoint in your module.config.php file of your application.
API Tools ship a version control with laminas-api-tools/api-tools-versioning. For how to configure the access to a specific version of your API resources just have a look at the versioning documentation. For our purpose we just use the uri key for routes, that can have a [/v:version] in it 's route.
Since laminas-api-tools/api-tools installed the dependency module laminas-api-tools/api-tools-rest we can easily define our rest service. Just add the api-tools-rest key to your config/module.config.php of your application.
These settings define some major points for your rest service. Under the listener key you define the resource class. With every call of the defined route route_name this class will be dispatched to handle all entity or collection requests. As you can see you don 't need a controller class for your REST service. All will be handled in the class we mentioned under the listener key. For a full description of all available user config keys have a look at the github repository.
From my point of view, the settings are enormously important in terms of security. Hereby you ensure which Accept Header information and which Content Type is accepted by your API. Everything that does not match these settings will be answered with a 406 Not Accetbale or a 415 Unsupported Media Type. For a complete list of content negotiation settings have a look at the respective github repository.
This is the simplest form of adding content validation. You can define a single input filter spec for every http method allowed for your service. For a deeper understanding have a look at the configuration specs in the github respository.
03c5feb9e7