We take a look at Uptime Kuma, an open-source, self-hosted monitoring tool for websites, APIs, and services. It allows you to keep track of the uptime, downtime, and response times of your applications. One of the recommended ways to deploy Uptime Kuma is to use Docker containers, as they allow for easy installation, scaling, and management.
The post Uptime Kuma: Open-source monitoring with Docker support first appeared on 4sysops.
En matière de création musicale, il y a souvent une étape qui casse un peu la tête, c’est le mastering. Il s’agit de la dernière touche qu’on apporte à un morceau de musique en relevant certaines de ces caractéristiques. On peut par exemple ajuster certaines fréquences, améliorer l’aspect stéréo, retirer certains parasites sonores…etc pour avoir quelque chose de très léché avec un son propre et optimisé pour tous les systèmes de diffusion du vinyl au streaming en passant par le CD.
Heureusement, pour cette étape, il y a des outils qui font également le boulot. C’est par exemple le cas de ce projet open source codé en Python et nommé Matchering, qui prend en entrée votre morceau ainsi que le morceau qui sera utilisé comme référence.
L’algo de matchering va vous permettre de donner à votre morceau de musique la même sonorité que celui de votre artiste préféré. Cela permet également de mettre toutes les chansons d’un même album au diapason. Et pour cela, Matchering analyse le morceau de référence et en extrait la moyenne quadratique (RMS), la réponse en fréquence, l’amplitude, mais également la spatialisation stéréo. Puis applique ces mêmes paramètres à votre morceau.
Comme c’est un logiciel libre, vous pouvez l’installer via Docker sur votre propre machine. C’est également une lib python, donc vous pouvez intégrer ses fonctionnalités dans vos outils.
Connexionimport matchering as mg
# Sending all log messages to the default print function
# Just delete the following line to work silently
mg.log(print)
mg.process(
# The track you want to master
target="my_song.wav",
# Some "wet" reference track
reference="some_popular_song.wav",
# Where and how to save your results
results=[
mg.pcm16("my_song_master_16bit.wav"),
mg.pcm24("my_song_master_24bit.wav"),
],
)Et si tout cela n’est pas possible pour vous mais que vous voulez quand même tester, il y a des services (avec quelques crédits gratuits) qui l’ont implémenté comme Songmastr et Moises.
Maintenant si vous êtes producteur ou ingénieur son, ça peut valoir le coup de vous pencher sur Docker en cliquant ici.
ManageEngine OpManager provides a comprehensive solution to monitor on-prem servers, networking, storage, cloud, virtualization, containers, and more.
The post ManageEngine OpManager: Comprehensive monitoring for on-prem, cloud, and containers first appeared on 4sysops.Two recent message center notifications highlight closer integration between SharePoint Online and Azure AD. MC526130 (11 March) says that new tenants created after March 31, 2023 will automatically enable the SharePoint Online integration with Azure B2B integration. Existing tenants aren’t impacted by this change. The associated update, also scheduled for roll-out in late March, is MC525663 (10 March). The news here is that SharePoint Online site sharing will use the Azure B2B Invitation manager instead of the legacy SharePoint Invitation Manager (Microsoft 365 roadmap item 117557).
The two updates rationalize existing sharing methods with external users and focus on Azure AD as the driving force for managing invitations. The journey toward Azure AD B2B Collaboration started in 2021, so it’s been a while coming. The project makes a lot of sense for both customers and Microsoft (their gain is through reduced engineering expenses).
Ten years ago, it was reasonable for SharePoint to manage site sharing invitations. Today, when the site collection-based architecture is replaced by single-sites and most sharing occurs through Microsoft 365 groups and Teams, it’s illogical for SharePoint Online to have its own mechanism. 280 million monthly active Teams users create a lot of work for SharePoint.
Another factor is that site sharing with external users is a relatively uncommon action today. Most external users join groups or teams and gain access to the group-connected site. Although non-group connected sites do exist, they’re in the minority and some of those sites (like hub and communication sites) aren’t candidates for sharing with external people. And of course, even site owners might be blocked from sharing sites by a sensitivity label.
Overall, I don’t think the change will disrupt many organizations. As Microsoft notes “You may want to review your Azure B2B Invitation Manager policies.” Two policies are worthy of note. The first is the Azure B2B Collaboration policy, which includes an allow or deny list (but not both) of domains.
The policy is now found under Collaboration restrictions in the External Identities section of the Azure AD admin center (Figure 1). It is commonly used to block sharing with consumer domains (deny list) or to restrict collaboration to a set of known domains belonging to partner organizations (allow list). If the organization already supports guest accounts, it’s likely that the collaboration policy already exists. Even so, changes like this are useful reminders of the need for regular review of any policy that affects how external people access tenant resources.
Azure AD cross-tenant access policies are a more powerful and flexible mechanism to control external access through both Azure B2B collaboration and Azure AD direct connect (used for Teams shared channels). Cross-tenant access policies are still relatively new and don’t need to be implemented unless required for a specific reason, so your tenant might not use them yet.
Although the Azure AD B2B Collaboration policy is likely to dominate for the immediate future, over time, I expect a slow transition to take advantage of the granular control available in cross-tenant access policies. When an organization changes over, SharePoint Online will take advantage. Leveraging advances made in Azure AD is an excellent reason for SharePoint Online to embrace Azure AD more fully.
Azure AD B2B collaboration works but that doesn’t mean that you don’t need to manage guest accounts. As more sharing happens, more guest accounts end up in your Azure AD. Some guest accounts are used once to share a document. Others are in ongoing use as guest members of groups and teams access shared documents. It’s a good idea to keep an eye on guest accounts and remove them as they become obsolete.
Support the work of the Office 365 for IT Pros team by subscribing to the Office 365 for IT Pros eBook. Your support pays for the time we need to track, analyze, and document the changing world of Microsoft 365 and Office 365.
Un groupe de hackers, se faisant appeler BlackCat, a prétendu avoir piraté la société de sonnettes connectées du groupe Amazon : Ring. Le message a été publié sur le darknet dans un anglais rudimentaire et laisse entendre que les pirates sont toujours en négociation. Le géant de la sonnette connectée affirme ne pas avoir été victime de ransomware, mais un de ses fournisseurs aurait été visé. Ring hacké ? Ring est, une entreprise américaine, spécialisée dans les sonnettes intelligentes avec […]If you own a SharePoint site, I am sure you followed all the best practices regarding the site security setup and permissions. However, you might also want to control the experience of the users who do not have access to the site just yet, but who might need one. Likewise, you might want to view pending access requests at any point in time and either approve or reject them. In addition, if you happened to share the site externally, you might want to track who accepted your invite and who did not. I know I listed a few different scenarios in this article, but they will all be answered by the wonderful feature of Site access requests. Buckle up and enjoy another sermon of wisdom from rabbi Zelfond. By the way, you might want to read this post till the end as I also cover some important and unintended consequences of SharePoint access Site Requests.
By default, on any given site, when the users who don’t have access to that site, when clicking on its URL, will get this message.
Here they can add a personal message and press the Request Access button, and request access to the site.
You can customize this page and either disable this button or control who the requests go to. Let me explain.
If you do not want users to bother you with these requests, you can disable them altogether.
Alternatively, you can also specify who the Site access requests will be emailed to. By default, they are sent to the Site Owners. However, you can also designate an alternate email address. It can be an email address of any user, and can even be an external email address as well. And you can also add a custom message to the request access page if necessary.
When the user requests access to the site, here is what happens:
If you ever want to see all the past and present, and pending SharePoint access Site Requests, this is how you do it.
What I also really like about this page above is that it allows you to view the status of pending invitations sent out to external users. So if you shared your site externally and wondering if external users accepted the invite or not, this is the page to view this on!
It is also very important to note what is actually happening to the site permissions when you accept the user request to access the site, as this might lead to some unintended consequences. Let me explain.
When you Accept a given access request, then navigate to Site Permissions (Gear Icon > Site Permissions), you will see the users automatically added to the SharePoint Site Members Group (those with Edit role)
Of course, you can change their role to Visitor or remove them altogether if necessary. However, this behavior can also lead to confusion and unintended consequences if your SharePoint site is connected to a Microsoft 365 Group (i.e., the site is part of Microsoft Teams).
One would expect that by requesting access to the site, they become a member of the whole Microsoft 365 Group (Teams, Outlook, Planner, etc.). But that is not the case. They are just given access to the site itself only. If you check the group membership, they won’t appear there.
So if you would like to add those users to the group itself and give them access to Teams, etc., you would need to add them as members of the group. By the way, I explained these two different models of security for a group-connected site in this article.
The post How to manage SharePoint access Site requests appeared first on SharePoint Maven.
NetCrunch 13 is the latest release of AdRem Software's flagship monitoring software, containing many new features and enhancements. The monitoring solution can monitor various physical, virtual, and network infrastructures. It provides real-time network monitoring, traffic analysis, alerts, and performance reporting.
The post NetCrunch 13: Real-time network monitoring, traffic analysis, alerts, and performance reporting first appeared on 4sysops.A very common requirement which is being request frequently is having a lookup table that points to multiple tables similar to the out of the box customer lookup type that can point out to either a contact or account.
This feature was released in July 2021 but I hadn’t the chance to try it till now and it came up with a challenge to using it which is Prefiltering this new type of lookup and I have searched and googled and everything and I really could not find someone who tried it, Many articles pointing out how to create this column typeand how it looks like but none really explained how to add prefiltration so it does not display all the records but show them as filtered based on a predefined criteria.
This article by Nick Doelman has a very good explanation to Polymorphic lookups.
This article describes how to do pre-filtration to a normal lookup type.
Also with the help of the XRMToolbox Polymorphic Lookup Creator it was very easy to create the polymorphic lookup which for the sake of the example below my lookup needed to point to either contact or user tables with a pre-search filter where first name = Mira
SO when it came to the prefiltration it was pretty easier than I thought and I just tried it and to my Surprise it worked, so all I did is used the normal way for lookup filtration but added a custom filter for each of my tables.
function FilterPolymporphicLookup(executionContext){
formContext = executionContext.getFormContext();
formContext.getControl("new_polymorphiclookupid").addPreSearch(filterPolymorphic);
}
function filterPolymorphic() {
var contactFilter = "<filter type='and'><condition attribute='firstname' operator='eq' value='Mira' /></filter>";
var userFilter = "<filter type='and'><condition attribute='firstname' operator='eq' value='Mira' /></filter>";
formContext.getControl("new_polymorphiclookupid").addCustomFilter(contactFilter, "contact");
formContext.getControl("new_polymorphiclookupid").addCustomFilter(userFilter, "systemuser");
}Multilookup
miraghaly
A very common requirement which is being request frequently is having a lookup table that points to multiple tables similar to the out of the box customer lookup type that can point out to either a contact or account.
This feature was released in July 2021 but I hadn’t the chance to try it till now and it came up with a challenge to using it which is Prefiltering this new type of lookup and I have searched and googled and everything and I really could not find someone who tried it, Many articles pointing out how to create this column typeand how it looks like but none really explained how to add prefiltration so it does not display all the records but show them as filtered based on a predefined criteria.
This article by Nick Doelman has a very good explanation to Polymorphic lookups.
This article describes how to do pre-filtration to a normal lookup type.
Also with the help of the XRMToolbox Polymorphic Lookup Creator it was very easy to create the polymorphic lookup which for the sake of the example below my lookup needed to point to either contact or user tables with a pre-search filter where first name = Mira
SO when it came to the prefiltration it was pretty easier than I thought and I just tried it and to my Surprise it worked, so all I did is used the normal way for lookup filtration but added a custom filter for each of my tables.
function FilterPolymporphicLookup(executionContext){
formContext = executionContext.getFormContext();
formContext.getControl("new_polymorphiclookupid").addPreSearch(filterPolymorphic);
}
function filterPolymorphic() {
var contactFilter = "<filter type='and'><condition attribute='firstname' operator='eq' value='Mira' /></filter>";
var userFilter = "<filter type='and'><condition attribute='firstname' operator='eq' value='Mira' /></filter>";
formContext.getControl("new_polymorphiclookupid").addCustomFilter(contactFilter, "contact");
formContext.getControl("new_polymorphiclookupid").addCustomFilter(userFilter, "systemuser");
}One of the biggest advantages of using a cloud platform like SharePoint is the ability to share documents with others by sharing links instead of attachments in the email. There are lots of advantages to this, all of which I documented in an earlier post. However, there is also another great set of features related to sharing when you share Word documents. So today, I want to explain a few different ways/modes available when sharing Word documents in SharePoint and OneDrive.
To clarify, in this article, I am not talking about whom you are sharing with, in other words, the different types of links you see when you try and share documents (i.e., Anyone with the link, People in your organization with the link, People with existing access, Specific people). I explained those types of links and the difference between them here. Instead, this article focuses on what the recipient will be able to do with the shared document (i.e., View or Edit).
When you share a Word document or any other type of Document (Excel, etc.) – you can choose between the Can view and Can edit type of mode. The View mode will just allow the user to:
Since the view mode does not allow the user to edit documents, versioning will remain unchanged, and no other versions will be created.
Edit mode will allow the recipient to also make changes to the document. As with View, this option is available for all file types (Excel, PowerPoint, etc.) To summarize, the Edit mode will allow the users to:
Since the recipient will have edit capabilities, there will be a change in versioning. Every time the doc is changed, another version is created. Many times when the user does not even make the changes, the version can still be created (i.e., the recipient just moved the cursor or added space somewhere inadvertently). This will register another version even if no intended changes have occurred.
The recipient’s changes will immediately be made to the document, and that change will be the latest and greatest from that moment on.
This permission level is only available when sharing Word documents (not Excel or PowerPoint). When this mode is chosen, the Word document will be shared with the recipient in the Review mode. That is when any changes the recipient makes will become marked-up suggestions and not the actual changes until the document owner approves or rejects them.
When the recipient changes the document shared with them in Review mode, all the changes become the suggested markups.
The owner of the document will see those changes and be able to either approve or reject them inside of the document or via the Review panel.
There will be two more versions created as a result. One for suggested changes made by the recipient in the Review mode and one for the Owner of the documents once the changes are either accepted or rejected.
The post 3 ways of sharing Word documents in SharePoint and OneDrive appeared first on SharePoint Maven.
Les développeurs se demandent souvent comment ils peuvent optimiser le SEO de leur SPA (Single Page Application) et quels résultats ils obtiendront dans le moteur de recherche Google (blogs, portfolios, site ecommerce...).
Ils se demandent également quelquefois à quel point il serait difficile de développer une application server-rendering.
Dans cet article, découvrez un guide pour bien démarrer avec Nuxt.js et le server-rendering de SPA.
Présentée en Février 2015 lors des Microsoft Techdays, S-Energy est une solution de monitoring des ressources énergétiques (eau, électricité et gaz) connectée dans Constellation conçue fin 2014 suite à une fuite d’eau sur ma chaudière. Avec Constellation, la plateforme d’interconnexion des objets connectés, applications et services, cela me permet d’afficher les consommations en temps sur […]
Cet article S-Electricity : connecter son compteur d’électricité en Wifi dans Constellation – le remake d’S-Energy avec un ESP8266 est apparu en premier sur Sebastien.warin.fr.
Suite à l’installation de la fibre Orange à mon domicile fin décembre, je vous propose ici une découverte de la fibre optique et notamment de la technologie GPON déployée par Orange. Vous découvrirez aussi comment configurer l’Internet, la TV et la téléphonie sans Livebox, en utilisant votre propre routeur, dans mon cas un Mikrotik RB3011 […]
Cet article Fonctionnement de la fibre Orange et remplacement de la Livebox par un routeur Mikrotik sous RouterOS – Petit aperçu de mon réseau local, du GPON, de l’IGMP, Asterisk et Cacti sans oublier Constellation est apparu en premier sur Sebastien.warin.fr.
feature
jcook127001
It would seem like the simplest thing in the world: show results in the PnP Modern Search Results Web Part in alphabetical order. My wanting to do this led to multiple conversations with my search guru Mikael Svenson (@mikaelsvenson) and the uncovering of some really useful variants on RefinableString in the SharePoint Online Managed Properties.
The new(ish? – it’s not clear how long they have been there) pre-created Managed Properties which are variants of RefinableString are now documented in Manage the search schema in SharePoint – SharePoint in Microsoft 365 | Microsoft Learn. Until I offered some updates recently, these variants weren’t in the article. I’m not sure I’d ever found this article before, but it seems to be the canonical list of Refinable Managed Properties, along with a lot of useful information about the Search Schema.
The new (to me, anyway) ones are in the last four rows of the following table in that article:
| Managed property type | Count | Multi | Query | Search | Retrieve | Refine | Sort | Managed property name range | Notes |
|---|---|---|---|---|---|---|---|---|---|
| Date | 10 | – | Query | – | – | – | – | Date00 to Date09 | |
| Date | 20 | Multi | Query | – | Retrieve | Refine | Sort | RefinableDate00 to RefinableDate19 | |
| Date | 2 | – | Query | – | Retrieve | Refine | Sort | RefinableDateInvariant00 to RefinableDateInvariant01 | * |
| Date | 5 | – | Query | – | Retrieve | Refine | Sort | RefinableDateSingle00 to RefinableDateSingle04 | |
| Decimal | 10 | – | Query | – | – | – | – | Decimal00 to Decimal09 | |
| Decimal | 10 | Multi | Query | – | Retrieve | Refine | Sort | RefinableDecimal00 to RefinableDecimal09 | |
| Double | 10 | – | Query | – | – | – | – | Double00 to Double09 | |
| Double | 10 | Multi | Query | – | Retrieve | Refine | Sort | RefinableDouble00 to RefinableDouble09 | |
| Integer | 50 | – | Query | – | – | – | – | Int00 to Int49 | |
| Integer | 50 | Multi | Query | – | Retrieve | Refine | Sort | RefinableInt00 to RefinableInt49 | |
| String | 200 | Multi | Query | – | Retrieve | Refine | Sort | RefinableString00 to RefinableString199 | |
| String | 40 | Multi | Query | – | Retrieve | Refine | Sort | RefinableStringFirst00 to RefinableStringFirst39 | * |
| String | 10 | Multi | Query | – | Retrieve | Refine | Sort | RefinableStringLn00 to RefinableStringLn09 | ** |
| String | 50 | – | Query | – | Retrieve | Refine | Sort | RefinableStringWbOff00 to RefinableStringWbOff49 | *** |
| String | 50 | Multi | Query | – | Retrieve | Refine | Sort | RefinableStringWbOffFirst00 to RefinableStringWbOffFirst49 | *, *** |
* Mappings to crawled properties – Include content from the first crawled property that is not empty, based on the specified order.
** Language neutral word breaker
*** Complete Matching
As you can see, each of the additional RefinableString* Managed Properties has something a little different about it, as indicated in the Notes.
Need to know more? Feel free to ask your questions in the comments.
This is a quick tip about a SNAFU which caught me up today. I got to do a “Doh!” in front of a client, which is always fun. Hopefully this will save you the same embarrassment.
Filtering News pages based on some metadata applied to the pages is a thing, and has been for a good, long time. I knew it should work, and pretty easily at that.
When I was on the call, I had added a metadata column to the Site Pages library. Simple. I went and put the page with the News Web Part into edit mode and looked in the Filter section for Page properties. No joy. Instead I was seeing:
Managed Properties are awesome, and I set them up all the time so I can build search-driven solutions, usually with the PnP Modern Search Web Parts, which, as I’ve said before, are the bees knees. But I knew there should be an option to filter based on Page properties instead. Had something changed? Was it better? I wasn’t sure.
I fired up my MVP communication channel and asked if things had indeed changed. As I expected, Susan Hanley (@susanhanley) responded almost right away.
Look to see what the Source is for News. When it is a single site (i.e., the site you are on), you can filter using Page properties. When you are selecting news from multiple sites, you will not see the Page Properties option – just Managed property.
Doh! I hadn’t even though to check that setting! A simple change at the top of the News Web Part properties to use This site as the source, and Page properties was back where I expected it.
This makes sense if you think about it. The Page properties in Site Pages libraries probably wouldn’t be consistent across multiple sites, so Managed properties makes more sense. Within one site, the Site Pages library is a single source, so has to be consistent with itself.
I do think there could be some in-Web-Part assistance for this with a slightly better UI, though. Maybe just an info bubble like the Enable audience targeting section right below it?
As you might expect, Greg Zelfond (@gregoryzelfond) has a great post about all this if you want to understand it better:
How to manage categories of news using custom metadata – SharePoint Maven
